Docs/Sources/Birthstone Grounding Data

Birthstone Grounding Data

Lookup Birthstone Information

OperationalCredits 2 per callp50 272msReference Data

Overview

Perfect for jewelry applications, astrology tools, gift recommendation engines, or any application that needs accurate birthstone data. Returns both traditional and modern birthstone options for each month.

Live Test Birthstone Grounding Data Source →

The tool

Once your client is connected to the VerveContext server, this appears in its tool list as BirthstoneGroundingData. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call
{
  "name": "BirthstoneGroundingData",
  "arguments": {
    "month": "5"
  }
}

You do not name the tool yourself; the model picks it. Asking about 5 in the terms this source covers is enough for it to reach for BirthstoneGroundingData on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every source in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

ArgumentTypeDescription
monthRequiredstringThe month number (1-12) or name
12345678+16

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "count": 1,
    "birthstones": [
      {
        "month": 5,
        "monthName": "May",
        "primaryStone": "Emerald",
        "alternateStones": [
          "Chrysoprase",
          "Agate"
        ],
        "color": "Green",
        "meaning": "Rebirth, love, fertility",
        "zodiacSigns": [
          "Taurus",
          "Gemini"
        ],
        "hardness": 7.5,
        "mineralFamily": "Beryl",
        "anniversaryYear": 55
      }
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

FieldTypeExampleDescription
countnumber1Number of months returned
birthstonesarray[1]The birthstones for each month requested
birthstones.0.monthnumber5Birth month number from 1 to 12
birthstones.0.monthNamestringMayFull name of the birth month
birthstones.0.primaryStonestringEmeraldPrimary gemstone for the month
birthstones.0.alternateStonesPremiumarray["Chrysoprase","Agate"]Alternate gemstones associated with month
birthstones.0.colorstringGreenTraditional color associated with stone
birthstones.0.meaningPremiumstringRebirth, love, fertilitySymbolism and meaning of the birthstone
birthstones.0.zodiacSignsarray["Taurus","Gemini"]Zodiac signs associated with month
birthstones.0.hardnessPremiumnumber7.5Mohs hardness rating of gemstone
birthstones.0.mineralFamilyPremiumstringBerylMineral classification family
birthstones.0.anniversaryYearPremiumnumber55Anniversary year associated with stone

Why ground on it

A model can produce something that looks like this answer from its training data, and be confidently out of date or simply wrong. This source returns the current value in a shape you can check, which is the difference between an answer you can cite and one you have to hedge.

Point an evaluation at count: it is the field most worth pinning a claim to, and it is either present and current or absent — never plausibly invented.

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

StatusWhat it means
400 / 422The arguments did not validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Blocked by a key restriction or an IP allow-list. Never a bad identity.
404This source is not part of VerveContext. Check the catalog.
429Out of credits, or a brief rate limit. The message tells them apart.

A call costs 2 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Jewelry E-commerce
Display relevant birthstone options for gift recommendations
Astrology Applications
Show birthstones associated with zodiac signs
Gift Finder Tools
Suggest personalized gemstone gifts based on birth month
Educational Content
Provide gemstone information for learning applications

Other ways to use Birthstone Grounding Data

Set up Birthstone Grounding Data on VerveContext, or reach the same source a different way. Your VerveContext account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →

More in Reference Data:

Was this page helpful?