Skip to main content
Glama

resolve_airport

Look up an airport by ICAO/IATA code or partial name using an offline bundled reference database, returning matches without API credits or credentials.

Instructions

Resolve an airport from an ICAO/IATA code or a name fragment.

Offline and free: reads the bundled OurAirports reference database, so it
costs no API credits and works with no credentials configured.

Args:
    query: ICAO (ESGG), IATA (GOT), or part of an airport name.
    limit: Maximum matches to return (1-20).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "resolve_airport"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful traits: it reads a bundled OurAirports database, runs offline, requires no credentials, and consumes no API credits. It omits what happens when nothing matches, whether multiple matches are ranked or truncated, and how 'limit' interacts with ambiguity.

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?

Front-loaded with the one-line purpose, then the offline/credential-free context, then a clean Args block. No filler sentences; the Args formatting is practical rather than redundant.

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

Completeness4/5

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

An output schema exists, so return values need not be explained, and both parameters are documented in the description. For a two-parameter lookup tool this is nearly complete; the main residual gap is behavior on zero or many matches.

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 description coverage is 0%, so the description must compensate, and it largely does: it explains the three accepted query forms with concrete examples (ESGG, GOT, name fragment) and gives the limit range 1-20, which the schema itself does not encode. It could further clarify default/collision behavior when a fragment is short and matches many airports.

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

Purpose4/5

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

States a specific verb (resolve) and resource (airport) plus the accepted input forms (ICAO, IATA, name fragment). It implicitly separates itself from siblings like airport_live_traffic or airport_weather by framing this as an offline reference lookup, but it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The 'offline and free... costs no API credits and works with no credentials' line is a real usage signal that steers toward this tool over paid or credentialed ones. However, there is no explicit when-to-use vs alternatives statement, no note about preferring exact codes over fuzzy fragments, and no guidance for ambiguous multi-match results.

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