Skip to main content
Glama

Asia Miles Calculator

Search Airports & IATA Codes

search_airports
Read-only

Search airports by IATA code, city name (English or Chinese), or airport name.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesCity name, airport name, or IATA code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's job is lighter. It adds the searchable-field set but omits anything about result ordering, match behavior (exact vs. partial), or what the response contains.

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?

One sentence, zero filler, and the accepted input types are front-loaded where an agent will read them first.

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

Completeness3/5

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

For a simple two-parameter lookup this is serviceable, but with no output schema the agent has no idea what a result looks like (does it include the IATA code, city, country?) and the paging/limit parameter is undocumented in prose. Slightly short of complete.

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?

The description adds real meaning for 'query' beyond the schema's 'City name, airport name, or IATA code' by specifying English or Chinese city names. The second parameter (limit, default 10, max 25) is never mentioned in the description, and with 50% schema coverage that leaves a gap.

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?

Specific verb ('Search') plus resource ('airports') and enumerates the three match keys (IATA code, city name, airport name). It does not differentiate from siblings, but the given siblings (calculate_asia_miles, get_direct_routes) are unrelated lookups, so the description is clear enough on its own.

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?

Usage is implied by the list of accepted search keys, but there is no explicit when-to-use statement, no note on what happens if a query matches multiple airports, and no guidance on choosing between code vs. name queries. Adequate but inference-dependent.

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.