Country Grounding Data for AI Agents
The tool
Ground agents in verifiable country reference data — 250 nations with capitals, codes and languages — so geo answers rest on real records.
Once your client is connected to the VerveContext MCP server, this appears in its tool list as CountryGroundingDataforAIAgents. 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": "CountryGroundingDataforAIAgents",
"arguments": {
"country": "USA"
}
}What that looks like in a conversation
You don't name the tool — the model picks it. Asking about USA in the terms this source covers is enough for it to reach for CountryGroundingDataforAIAgents 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 |
|---|---|---|---|
countryRequired | string | USA | The Country name or ISO code of the country for which you want to get the data (e.g., USA) |
majorcitiesPremium | boolean | true | Specify if you would like to return all major cities of the country found |
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": {
"search": "USA",
"countries": [
{
"name": {
"common": "United States",
"official": "United States of America",
"native": {
"eng": {
"official": "United States of America",
"common": "United States"
}
}
},
"tld": [
".us"
],
"cca2": "US",
"ccn3": "840",
"cca3": "USA",
"cioc": "USA",
"independent": true,
"status": "officially-assigned",
"capital": [
"Washington D.C."
],
"altSpellings": [
"US",
"USA",
"United States of America"
],
"region": "Americas",
"subregion": "North America",
"languages": {
"eng": "English"
},
"latlng": [
38,
-97
],
"landlocked": false,
"flag": "🇺🇸"
}
]
}
}Fields
| Field | Type | Example | Description |
|---|---|---|---|
search | string | The search term or country code used in the lookup request | |
countries | array[1] | Array of country objects matching the search criteria | |
└ countries.0.name | object | The country's names: common, official, and native forms | |
└ countries.0.name.common | string | Common name of the country used in everyday reference | |
└ countries.0.name.official | string | Official formal name of the country recognized internationally | |
└ countries.0.name.nativePremium | object | Native language names of the country keyed by language code | |
└ countries.0.name.native.engPremium | object | ||
└ countries.0.name.native.eng.officialPremium | string | ||
└ countries.0.name.native.eng.commonPremium | string | ||
└ countries.0.tld | array | Top-level domains associated with the country | |
└ countries.0.cca2 | string | Two-letter country code following ISO 3166-1 alpha-2 standard | |
└ countries.0.ccn3Premium | string | Three-digit country code following ISO 3166-1 numeric standard | |
└ countries.0.cca3 | string | Three-letter country code following ISO 3166-1 alpha-3 standard | |
└ countries.0.ciocPremium | string | International Olympic Committee country code for sports competitions | |
└ countries.0.independentPremium | boolean | Indicates whether the country is politically independent | |
└ countries.0.statusPremium | string | Official assignment status of the country code in international records | |
└ countries.0.capital | array | Array of capital city or cities of the country | |
└ countries.0.altSpellings | array | Alternative spellings and abbreviations of the country name | |
└ countries.0.region | string | Geographic region where the country is located globally | |
└ countries.0.subregion | string | More specific geographic subregion classification of the country | |
└ countries.0.languages | object | Object mapping language codes to official language names | |
└ countries.0.languages.eng | string | ||
└ countries.0.latlngPremium | array | Array with latitude and longitude coordinates for country center | |
└ countries.0.landlockedPremium | boolean | Indicates whether the country has no ocean or sea coastline | |
└ countries.0.flag | string | Unicode flag emoji representation of the country |
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 search: 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 Country Grounding Data for AI Agents
Set up Country 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 CountryGroundingDataforAIAgents?
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.