Skip to main content
Glama

Find airports by IATA or ICAO code, name or distance

airports
Read-only

Airport lookup in a bundled OurAirports extract (public domain, dated in the answer): by IATA or ICAO code, by name or city words, or the nearest airports within a radius (up to 300 km) of a point. Covers large and medium airports and every airport with an IATA code; small airports without one are left out. Name, codes, type, city, country, coordinates, elevation and Wikipedia link. No time zone (not in the source). Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "airports"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoName or city words, 3 to 60 characters (one of code, q or lat and lon)
latNoLatitude for the nearest search (with lon)
lonNoLongitude for the nearest search (with lat)
codeNoIATA (3 letters) or ICAO (4 letters) code (one of code, q or lat and lon)
limitNoAirports to return, 1 to 20, default 10
radiusKmNoSearch radius for the nearest search, 1 to 300, default 300

Output Schema

NameRequiredDescriptionDefault
countNo
queryNo
sourceNo
airportsNo
dataDateNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly/openWorld annotations, it discloses source provenance and freshness ('public domain, dated in the answer'), a known data gap ('No time zone (not in the source)'), and a full pricing/auth model: $0.002 per successful call, paid via x402 in USDC on Base, Solana and other networks, with failed calls free. That cost and payment requirement is exactly the kind of behavior an agent cannot infer from annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, and each subsequent sentence contributes a distinct fact (coverage, returned fields, missing field, price). It is a single dense paragraph rather than a list, and the price clause is long, but no sentence is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain returns, yet it still enumerates the fields (codes, type, city, country, coordinates, elevation, Wikipedia) and flags the absent time zone. Combined with the coverage boundary and the payment model, an agent has everything needed to call this correctly and understand what it costs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning on top: it groups the parameters into three mutually exclusive lookup modes and ties radiusKm to the nearest-search mode with a 300 km ceiling. It does not add format detail for lat/lon as strings or limit semantics beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the specific resource (airports in a bundled OurAirports extract) and all three lookup modes: IATA/ICAO code, name or city words, and nearest-within-radius. The title and first sentence together let an agent distinguish this from generic geocoding siblings like 'distance' or 'address_parse' without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly states the conditions under which each mode applies (radius search needs a point, capped at 300 km) and defines data coverage — large/medium airports plus every airport with an IATA code, excluding small airports without one. It stops short of naming an alternative tool or saying when NOT to use this one, but the mode-selection context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources