Skip to main content
Glama

Airports

airports
Read-onlyIdempotent

Airport directory, name, IATA/ICAO codes, country, GPS, timezone.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchNoFree-text, name / city
iata_codeNo3-letter IATA code
icao_codeNo4-letter ICAO code
country_iso2NoISO 3166-1 alpha-2 country

Output Schema

NameRequiredDescriptionDefault
dataNoArray of airport objects
paginationNoPagination metadata

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / data / items / properties / phone_number / description
      Previous value: -"Airport phone number, null when unknown. Declared null-only until 2026-08-13 — a one-sample inference artifact, not the real type."New value: +"Airport phone number, null when unknown. Declared null-only until 2026-08-13, a one-sample inference artifact, not the real type."
  2. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Free-text — name / city"New value: +"Free-text, name / city"
  3. Changed2 schema fields changed
    • addedOutput schema / properties / data / items / properties / phone_number / description
      Added value: +"Airport phone number, null when unknown. Declared null-only until 2026-08-13 — a one-sample inference artifact, not the real type."
    • changedOutput schema / properties / data / items / properties / phone_number / type
      Previous value: -"null"New value: +[
      +  "string",
      +  "null"
      +]
  4. Changed10 schema fields changed
    • addedOutput schema / properties / data / items / properties / airport_id
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / data / items / properties / city_name
      Removed value: -{
      -  "description": "City name",
      -  "type": "string"
      -}
    • changedOutput schema / properties / data / items / properties / country_name / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • addedOutput schema / properties / data / items / properties / geoname_id
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / data / items / properties / gmt_offset_seconds
      Removed value: -{
      -  "description": "GMT offset in seconds",
      -  "type": "number"
      -}
    • addedOutput schema / properties / data / items / properties / id
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / data / items / properties / latitude / type
      Previous value: -"number"New value: +"string"
    • changedOutput schema / properties / data / items / properties / longitude / type
      Previous value: -"number"New value: +"string"
    • addedOutput schema / properties / data / items / properties / phone_number
      Added value: +{
      +  "type": "null"
      +}
    • addedOutput schema / properties / pagination / properties / total
      Added value: +{
      +  "type": "number"
      +}
  5. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "iata_code": "JFK"
      +  },
      +  {
      +    "country_iso2": "GB",
      +    "search": "London"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "description": "Array of airport objects",
      +      "items": {
      +        "properties": {
      +          "airport_name": {
      +            "description": "Full airport name",
      +            "type": "string"
      +          },
      +          "city_iata_code": {
      +            "description": "City IATA code",
      +            "type": "string"
      +          },
      +          "city_name": {
      +            "description": "City name",
      +            "type": "string"
      +          },
      +          "country_iso2": {
      +            "description": "ISO 3166-1 alpha-2 country code",
      +            "type": "string"
      +          },
      +          "country_name": {
      +            "description": "Country name",
      +            "type": "string"
      +          },
      +          "gmt": {
      +            "description": "GMT offset",
      +            "type": "string"
      +          },
      +          "gmt_offset_seconds": {
      +            "description": "GMT offset in seconds",
      +            "type": "number"
      +          },
      +          "iata_code": {
      +            "description": "3-letter IATA code",
      +            "type": "string"
      +          },
      +          "icao_code": {
      +            "description": "4-letter ICAO code",
      +            "type": "string"
      +          },
      +          "latitude": {
      +            "description": "Latitude coordinate",
      +            "type": "number"
      +          },
      +          "longitude": {
      +            "description": "Longitude coordinate",
      +            "type": "number"
      +          },
      +          "timezone": {
      +            "description": "IANA timezone",
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "pagination": {
      +      "description": "Pagination metadata",
      +      "properties": {
      +        "count": {
      +          "type": "number"
      +        },
      +        "limit": {
      +          "type": "number"
      +        },
      +        "offset": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    }
      +  },
      +  "type": "object"
      +}
  6. First observed

TDQS

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description adds nothing beyond those annotations — no note on result cardinality, whether a code lookup returns a single record or a list, or how pagination behaves. The field list it does provide duplicates what the output schema already exposes.

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

Conciseness3/5

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

It is a single short fragment with no wasted words, but that brevity comes at the cost of being a verbless field list rather than a front-loaded statement of function. Conciseness here shades into under-specification.

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

Completeness2/5

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

With six optional parameters, pagination, and a free-text search field, the definition should at minimum say how lookups resolve and how filters interact; it does not. The existence of an output schema excuses it from describing return values, but the input-side behavior remains unexplained.

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

Parameters3/5

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

Schema description coverage is 67%, and the description's mention of name, IATA/ICAO codes and country loosely maps to those parameters, so it is consistent with the schema baseline. It says nothing about search semantics (free-text over name/city), limit/offset behavior, or how multiple filters combine — the areas the schema leaves least specified.

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

Purpose3/5

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

The description identifies the resource as an airport directory and enumerates the fields it carries (name, IATA/ICAO, country, GPS, timezone), so an agent knows it is an airport lookup. But it is a bare noun phrase with no verb and no statement of scope, and it does not distinguish itself from siblings like airlines, aviationstack_cities or aviationstack_countries, which plausibly overlap.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all — no mention of looking up a specific airport by code versus searching by name/city, and no routing to or away from related tools such as airlines or cities. The agent must infer all invocation context from the schema examples.

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.