Skip to main content
Glama

Find airports

find_airports
Read-only

Look up airports and city codes by name, or list the airports near an airport code. Use it to turn a city name into the IATA code a flight search with the other tools takes.

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": "find_airports"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearNoan IATA airport code, to list the airports near it; give this or query
queryNoa city or airport name or the start of one; give this or near

Output Schema

NameRequiredDescriptionDefault
placesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / near / description
      Previous value: -"an IATA code, or lat,lon, to list the airports near it; give this or query"New value: +"an IATA airport code, to list the airports near it; give this or query"
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety and scope profile is covered by structured fields. The description adds the useful behavioral framing that results are IATA codes intended to feed other tools, but says nothing about result counts, ambiguity when a name matches multiple airports, or the meaning of "near" (radius/distance).

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

Conciseness5/5

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

Two sentences, both earning their place: the first states capability and the two modes, the second states the downstream purpose. The capability is front-loaded and there is no filler or repetition.

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?

For a two-parameter lookup tool with an output schema and full annotation coverage, the description covers both operating modes and the intended downstream use. The only real gap is the lack of any hint about how results are ordered or truncated when many airports match, which is minor given the output schema exists.

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 100%, and the schema already states that either parameter may be given and that query accepts a name prefix. The description restates the same two modes at a higher level without adding format, prefix-matching, or precedence details beyond the schema, so baseline 3 applies.

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?

The description names the resource and both modes explicitly: "look up airports and city codes by name, or list the airports near an airport code." That is a concrete verb+resource statement an agent can act on, and none of the listed siblings (cheapest_routes, route_fares, meet_link, where_to_meet) overlap with airport lookup, so ambiguity is low even without naming an alternative.

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 gives clear situational guidance: "Use it to turn a city name into the IATA code a flight search with the other tools takes," which tells the agent exactly where this tool sits in a workflow. It stops short of stating when NOT to use it or how to choose between the query and near modes, leaving that to the schema.

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