Nobel Prize Grounding Data for AI AgentsNobel Prize Grounding Data for AI Agents

OnlineCredit Usage:1 per callTool:NobelPrizeGroundingDataforAIAgents

The tool

Ground agents in verifiable Nobel laureate records so answers about winners, years and categories rest on sourced facts, not recall.

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

Tool call
{
  "name": "NobelPrizeGroundingDataforAIAgents",
  "arguments": {}
}

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.

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

Per-client setup — Claude Desktop, 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.

ArgumentTypeExampleDescription
firstnamestringAlbertThe first name of the Nobel Prize winner to get information about
lastnamestringEinsteinThe last name of the Nobel Prize winner to get information about
categorystringPhysicsThe category of the Nobel Prize to get information about One of: Physics, Chemistry, Medicine, Literature, Peace, Economics.
yearPremiuminteger1921The year of the Nobel Prize to get information about

What the model gets back

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

Result
{
  "status": "ok",
  "error": null,
  "data": {
    "count": 1,
    "filteredOn": [
      "firstName",
      "lastName",
      "category",
      "year"
    ],
    "nobelPrizes": [
      {
        "firstName": "Albert",
        "lastName": "Einstein",
        "born": "1879-03-14",
        "died": "1955-04-18",
        "countryborn": "Germany",
        "countrybornCode": "DE",
        "born city": "Ulm",
        "diedCountry": "USA",
        "diedCountryCode": "US",
        "diedCity": "Princeton NJ",
        "gender": "male",
        "year": "1921",
        "category": "Physics",
        "motivation": "for his services to Theoretical Physics and especially for his discovery of the law of the photoelectric effect",
        "organization": "Kaiser-Wilhelm-Institut (now Max-Planck-Institut) für Physik",
        "organizationCity": "Berlin",
        "organizationCountry": "Germany"
      }
    ]
  }
}

Fields

Fields marked Premium need a paid plan. On a plan without them the key is absent rather than wrong, so a model never reasons over a substituted value.
FieldTypeExampleDescription
countnumber1Total number of Nobel Prize winners matching the criteria
filteredOnarray["firstName","lastName","category"]List of filter fields applied to the query results
nobelPrizesarray[1]list of rowsArray of Nobel Prize winner records with complete biographical data
nobelPrizes.0.firstNamestringAlbertFirst name of the Nobel Prize winner
nobelPrizes.0.lastNamestringEinsteinLast name of the Nobel Prize winner
nobelPrizes.0.bornPremiumstring1879-03-14Birth date in YYYY-MM-DD format
nobelPrizes.0.diedPremiumstring1955-04-18Death date in YYYY-MM-DD format or null
nobelPrizes.0.countrybornPremiumstringGermanyCountry name where the laureate was born
nobelPrizes.0.countrybornCodePremiumstringDEISO country code of birth country (two letters)
nobelPrizes.0.born cityPremiumstringUlmCity or town where laureate was born
nobelPrizes.0.diedCountryPremiumstringUSACountry name where the laureate died
nobelPrizes.0.diedCountryCodePremiumstringUSISO country code of death country (two letters)
nobelPrizes.0.diedCityPremiumstringPrinceton NJCity or town where laureate died
nobelPrizes.0.genderPremiumstringmaleGender of the Nobel Prize winner
nobelPrizes.0.yearstring1921Year the Nobel Prize was awarded
nobelPrizes.0.categorystringPhysicsNobel Prize category (Physics, Chemistry, Medicine, Literature, Peace, Economics)
nobelPrizes.0.motivationPremiumstringfor his services to Theoretical Physics and especially for his discovery of the law of the photoelectric effectOfficial Nobel Prize motivation citation explaining the award
nobelPrizes.0.organizationPremiumstringKaiser-Wilhelm-Institut (now Max-Planck-Institut) für PhysikOrganization or institution affiliated with the laureate
nobelPrizes.0.organizationCityPremiumstringBerlinCity where the affiliated organization is located
nobelPrizes.0.organizationCountryPremiumstringGermanyCountry where the affiliated organization is located

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 with 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 with a sentence the model can act on, not a bare status code.

StatusWhat it means
400 / 422The arguments didn't validate. The message names the offending one.
401The OAuth session is invalid or expired — reconnect the server.
403Out of credits. Not a bad key — the month's allowance is spent.
404This source isn't part of VerveContext. Check the catalog.
429Brief rate limit. Retrying after a moment succeeds.

Other ways to use Nobel Prize Grounding Data for AI Agents

Set up Nobel Prize Grounding Data for AI Agents 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.APIVerveReference →
Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKitReference →
Use it in Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheetsReference →

Frequently asked questions

Do I have to tell the agent to use NobelPrizeGroundingDataforAIAgents?

No. The tool's name and description are in the model's context once the server is connected, so it selects the tool when the question calls for it. Naming it explicitly works too and is useful when you want to force the call.

Does connecting the server expose every tool at once?

Yes — one connection lists the whole VerveContext catalog. Clients with a tool budget can usually filter the list; the credit cost is per call, so an unused tool costs nothing.

What does a call cost?

1 credit each time the tool actually runs. A model that reasons about the tool without calling it costs nothing.

Is there a REST version of this?

Yes — the same source is available as a plain HTTPS endpoint on APIVerve, linked above. Same data, same credits, same account.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?