Skip to main content
Glama

search_airports_near_zip

Find general-aviation airports within a radius of a US ZIP code, ordered by distance (nearest first). Returns each airport with distance_nm. Useful for "what airports are near me / near 07666".

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": {
      "zip": "<zip>"
    },
    "name": "search_airports_near_zip"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit US ZIP code, e.g. 07666.
radiusNoSearch radius in nautical miles — one of 25, 50, 100, 150, 200 (default 50).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It usefully adds result ordering (nearest first), a returned field (distance_nm), and the significant behavioral constraint that only general-aviation airports are returned — but it says nothing about result caps, pagination, or what happens with an invalid or non-US ZIP.

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?

Three short sentences, front-loaded with the core action and scope, followed by the return shape and then a usage cue. Every sentence carries information and nothing is 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?

For a simple two-parameter search with no output schema, the description covers purpose, ordering, and the key returned field. The only meaningful gap is expected result volume or truncation behavior when a large radius is used.

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 coverage is 100%, so both parameters are already fully documented in the schema, including the allowed radius values and the default of 50. The description adds no extra semantics such as the maximum returned results scaling with radius, so baseline 3 applies.

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?

States a specific verb (Find), a specific resource (general-aviation airports), and the exact scope (within a radius of a US ZIP code) plus result ordering. The 'general-aviation' qualifier and proximity framing clearly separate it from the sibling search_airports, which an agent would read as a keyword/name search.

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?

Gives a concrete when-to-use trigger with example phrasings ("what airports are near me / near 07666"). It does not name an alternative tool or state when-not to use it (e.g., when the user wants a specific airport by name, use get_airport), so routing guidance stops short of the top score.

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