Overview
Query the database by passing a 3-letter IATA code to retrieve the airport's official name, state, city, and country code. The dataset covers over 40,000 airports and receives weekly updates. Upgraded subscriptions can also query directly by 4-letter ICAO code and receive geographic coordinates, runway elevation, timezone identifiers, and alternate city names.
Live Test Airport Grounding Data for AI Agents Source →
The tool
Once your client is connected to the VerveContext server, this appears in its tool list as AirportGroundingDataforAIAgents. 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.
{
"name": "AirportGroundingDataforAIAgents",
"arguments": {
"iata": "MCI"
}
}You do not name the tool yourself; the model picks it. Asking about MCI in the terms this source covers is enough for it to reach for AirportGroundingDataforAIAgents 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"
}
}
}https://api.vervecontext.com/v1/mcpPer-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.
| Argument | Type | Description |
|---|---|---|
iataRequired | string | The IATA code of the airport for which you want to get the information (e.g., MCI) |
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.
{
"status": "ok",
"error": null,
"data": {
"icao": "KMCI",
"iata": "MCI",
"name": "Kansas City International Airport",
"city": "Kansas City",
"state": "Missouri",
"country": "US",
"elevation": 1026,
"lat": 39.2975997925,
"lon": -94.7138977051,
"tz": "America/Chicago",
"city_info": {
"name": "Kansas City",
"altName": "",
"country": "US"
}
}
}
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.
| Field | Type | Example | Description |
|---|---|---|---|
icao | string | KMCI | International Civil Aviation Organization airport code |
iata | string | MCI | International Air Transport Association airport code |
name | string | Kansas City International Airport | Official name of the airport |
city | string | Kansas City | City where the airport is located |
state | string | Missouri | State or province where airport is located |
country | string | US | Country code where airport is located |
elevationPremium | number | 1026 | Airport elevation in feet above sea level |
latPremium | number | 39.2975997925 | Airport latitude coordinate for mapping |
lonPremium | number | -94.7138977051 | Airport longitude coordinate for mapping |
tzPremium | string | America/Chicago | IANA timezone name for the airport location |
city_infoPremium | object | {…} | Additional city information including alternate names |
city_info.namePremium | string | Kansas City | Primary city name for the airport location |
city_info.altNamePremium | string | | Alternate name for the city if available |
city_info.countryPremium | string | US | Country code for the city location |
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 icao: 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.
| Status | What it means |
|---|---|
400 / 422 | The arguments did not validate. The message names the offending one. |
401 | The OAuth session is invalid or expired — reconnect the server. |
403 | Blocked by a key restriction or an IP allow-list. Never a bad identity. |
404 | This source is not part of VerveContext. Check the catalog. |
429 | Out 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
- Flight Booking Confirmation
- When passengers enter an airport code, travel sites translate the code into the full facility name and destination city on itineraries.
- Air Freight Routing
- Logistics platforms convert flight manifests containing IATA codes into verified destination countries and cities to plan regional ground transfers.
- Flight Plan Mapping
- To plot flight paths, aviation software queries ICAO codes on paid plans to map runway coordinates and airport elevation.
- Expense Report Auditing
- Audit corporate travel receipts by matching ticket codes against declared employee itineraries to catch incorrect destination claims.
Other ways to use Airport Grounding Data for AI Agents
Set up Airport 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.
Related
More in Transportation: