Historical Events Grounding Data
The tool
Historical Events is a simple tool for getting historical events. It returns a list of historical events.
Once your client is connected to the VerveContext MCP server, this appears in its tool list as HistoricalEventsGroundingData. 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": "HistoricalEventsGroundingData",
"arguments": {
"text": "moon landing"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about moon landing in the terms this source covers is enough for it to reach for HistoricalEventsGroundingData on its own.
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 |
|---|---|---|---|
textRequired | string | moon landing | The keyword for which you want to get the historical events (e.g., moon landing) |
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": 6,
"filteredOn": [
"text"
],
"events": [
{
"year": "1969",
"month": "05",
"day": "18",
"date": "1969/05/18",
"event": " Apollo program: ''Apollo 10'' (Tom Stafford, Gene Cernan, John Young) is launched, on the full dress-rehearsal for the Moon landing.",
"range": "May",
"granularity": "year"
},
{
"year": "1969",
"month": "05",
"day": "25",
"date": "1969/05/25",
"event": "Apollo program: ''Apollo 10'' returns to Earth, after a successful 8-day test of all the components needed for the upcoming first manned Moon landing.",
"range": "May",
"granularity": "year"
},
{
"year": "1969",
"month": "07",
"day": "20",
"date": "1969/07/20",
"event": " Apollo program: The lunar module ''Eagle'' lands on the lunar surface. An estimated 500 million people worldwide watch in awe as Neil Armstrong takes his historic first steps on the Moon at 02:56 UTC, the largest television audience for a live broadcast at that time.cite web|title=Manned Space Chronology: Apollo_11|url=<a href=\"http://www.spaceline.org/flightchron/apollo11.html|publisher=spaceline.org|accessdate=2008-02-06|\">http://www.spaceline.org/flightchron/apollo11.html|publisher=spaceline.org|accessdate=2008-02-06|</a> archiveurl= <a href=\"http://web.archive.org/web/20080214213826/http://www.spaceline.org/flightchron/apollo11.html|\">http://web.archive.org/web/20080214213826/http://www.spaceline.org/flightchron/apollo11.html|</a> archivedate= 14 February 2008 !--DASHBot--| deadurl= no}}cite web|title= Apollo Anniversary: Moon Landing quotInspired Worldquot|url=<a href=\"http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|publisher=nationalgeographic.com|accessdate=2008-02-06|\">http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|publisher=nationalgeographic.com|accessdate=2008-02-06|</a> archiveurl= <a href=\"http://web.archive.org/web/20080209140059/http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|\">http://web.archive.org/web/20080209140059/http://news.nationalgeographic.com/news/2004/07/0714_040714_moonlanding.html|</a> archivedate= 9 February 2008 !--DASHBot--| deadurl= no}}",
"range": "July",
"granularity": "year"
},
{
"year": "1969",
"month": "07",
"day": "20",
"date": "1969/07/20",
"event": "The ''Apollo 11'' astronauts return from the first successful Moon landing, and are placed in biological isolation for several days, on the chance they may have brought back lunar germs. The airless lunar environment is later determined to preclude microscopic life.",
"range": "July",
"granularity": "year"
},
{
"year": "1971",
"month": "02",
"day": "08",
"date": "1971/02/08",
"event": "Apollo program: ''Apollo 14'' returns to Earth after the third manned Moon landing.",
"range": "February",
"granularity": "year"
},
{
"year": "1973",
"month": "01",
"day": "07",
"date": "1973/01/07",
"event": "Elvis Presley's concert in Hawaii. The first worldwide telecast by an entertainer watched by more people than watched the Apollo moon landings.",Fields
| Field | Type | Example | Description |
|---|---|---|---|
count | number | Total number of historical events returned in results | |
filteredOnPremium | array | Array of filter criteria applied to generate results | |
events | array[6] | Array of historical event objects matching search criteria | |
└ events.0.yearPremium | string | Calendar year when the historical event occurred | |
└ events.0.monthPremium | string | Month number (01-12) when the event occurred | |
└ events.0.dayPremium | string | Day of month when the historical event occurred | |
└ events.0.datePremium | string | Full date in YYYY/MM/DD format for the event | |
└ events.0.event | string | Detailed description and text of the historical event | |
└ events.0.rangePremium | string | Named month range or period when the event occurred | |
└ events.0.granularityPremium | string | Precision level of date (year, month, or specific day) |
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 Historical Events Grounding Data
Set up Historical Events 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.
Frequently asked questions
Do I have to tell the agent to use HistoricalEventsGroundingData?
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.