Nobel Prize Grounding Data for AI Agents
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.
{
"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.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp"
}
}
}https://api.vervecontext.com/v1/mcpPer-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.
| Argument | Type | Example | Description |
|---|---|---|---|
firstname | string | Albert | The first name of the Nobel Prize winner to get information about |
lastname | string | Einstein | The last name of the Nobel Prize winner to get information about |
category | string | Physics | The category of the Nobel Prize to get information about One of: Physics, Chemistry, Medicine, Literature, Peace, Economics. |
yearPremium | integer | 1921 | The 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.
{
"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
| Field | Type | Example | Description |
|---|---|---|---|
count | number | Total number of Nobel Prize winners matching the criteria | |
filteredOn | array | List of filter fields applied to the query results | |
nobelPrizes | array[1] | Array of Nobel Prize winner records with complete biographical data | |
└ nobelPrizes.0.firstName | string | First name of the Nobel Prize winner | |
└ nobelPrizes.0.lastName | string | Last name of the Nobel Prize winner | |
└ nobelPrizes.0.bornPremium | string | Birth date in YYYY-MM-DD format | |
└ nobelPrizes.0.diedPremium | string | Death date in YYYY-MM-DD format or null | |
└ nobelPrizes.0.countrybornPremium | string | Country name where the laureate was born | |
└ nobelPrizes.0.countrybornCodePremium | string | ISO country code of birth country (two letters) | |
└ nobelPrizes.0.born cityPremium | string | City or town where laureate was born | |
└ nobelPrizes.0.diedCountryPremium | string | Country name where the laureate died | |
└ nobelPrizes.0.diedCountryCodePremium | string | ISO country code of death country (two letters) | |
└ nobelPrizes.0.diedCityPremium | string | City or town where laureate died | |
└ nobelPrizes.0.genderPremium | string | Gender of the Nobel Prize winner | |
└ nobelPrizes.0.year | string | Year the Nobel Prize was awarded | |
└ nobelPrizes.0.category | string | Nobel Prize category (Physics, Chemistry, Medicine, Literature, Peace, Economics) | |
└ nobelPrizes.0.motivationPremium | string | Official Nobel Prize motivation citation explaining the award | |
└ nobelPrizes.0.organizationPremium | string | Organization or institution affiliated with the laureate | |
└ nobelPrizes.0.organizationCityPremium | string | City where the affiliated organization is located | |
└ nobelPrizes.0.organizationCountryPremium | string | Country 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.
| Status | What it means |
|---|---|
400 / 422 | The arguments didn't validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Out of credits. Not a bad key — the month's allowance is spent. |
404 | This source isn't part of VerveContext. Check the catalog. |
429 | Brief 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.
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.