Skip to main content
Glama

Airports Worldwide: Airports near a point

airports__near
Read-onlyIdempotent

Airports (large/medium/small by default) within a radius of a point or UK postcode, nearest first. Free within the daily allowance, then $0.002 USDC per call via x402.

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

Input Schema

NameRequiredDescriptionDefault
latNoLatitude (or give a UK postcode)
lngNoLongitude
typeNolarge | medium | small | heliport | …
limitNoMax results (default 10)
postcodeNoUK postcode instead of lat/lng
radius_kmNoRadius in km (default 50, max 300)
scheduledNo1 = scheduled passenger service only

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive, so the safety profile is covered. The description adds genuinely non-structured behavior: the pricing model (free within daily allowance, then $0.002 USDC via x402) and result ordering (nearest first). It stops short of describing pagination or what happens with no location supplied.

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 tight sentences, front-loaded with what the tool returns and how it is scoped; the cost footnote is short and earns its place. No filler or repeated schema content.

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?

With an output schema present, return values need no explanation, and the description covers resource, default filtering, ordering, and cost. The one gap is behavior when neither lat/lng nor postcode is provided, especially since zero parameters are required.

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 coverage is 100%, so baseline is 3, and the description earns a bump by disclosing a default the schema omits: type defaults to large/medium/small. It also corroborates the lat/lng-vs-postcode alternative, though it adds no syntax or format detail for radius_km or scheduled.

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+resource (find airports near a point/postcode) plus the scope qualifiers that matter: which airport types are included by default, radius-based search, and nearest-first ordering. It clearly differentiates from siblings like airports__search (text lookup) and airports__navaids-near (different resource).

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 geometry of the description ('within a radius of a point or UK postcode'), but no explicit when-to-use, when-not, or named alternative (e.g., use airports__search for name lookup, or navaids-near for navaids) is given. An agent can infer the intent but must decide on its own when this beats the sibling tools.

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