Tanod MCP server

skypeek: look up an airport

lookup_airport

Read-onlyIdempotent

Retrieve airport details by ICAO, IATA, or name. Obtain runways, frequencies, location, and elevation for informational use.

Instructions

skypeek: Look up an airport by ICAO or IATA code or by name. For the distance between two use airport_distance. Returns an airport by ICAO, IATA or ident code (with runways: ends, length, width, surface, lighting, true headings; and radio frequencies), or up to 20 matches of a name or city search, optionally in one country: name, codes, type, position, elevation, country, region and municipality. Informational only: not for flight planning or navigation. Airports: OurAirports (public domain); the data may contain errors and no endorsement is implied. Answered from a bundled copy (no upstream call). A code with no airport is a 404 airport_not_found (not charged). Typically under 0.1 s (first call about 2 s). Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/airport-lookup-flight-distance-api.html

Input Schema

TableJSON Schema

Name	Required	Description
`code`	No	ICAO, IATA or airport ident (such as RPLL, MNL or KSFO). Send code or query.
`limit`	No	Most query results (1-20).
`query`	No	Name or city search (at most 100 characters). Send code or query.
`country`	No	ISO 3166-1 alpha-2 country filter for query (such as PH).

Output Schema

TableJSON Schema

Name	Required	Description
`count`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`source`	No
`airports`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, and the description piles on genuinely useful behavior: bundled copy with no upstream call, a 404 airport_not_found that is not charged, typical 0.1 s latency (first call ~2 s), USD 0.001 price, 5 free calls/IP/day, and an upstream data provenance/accuracy caveat.

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?

Purpose and the sibling routing are front-loaded, and the dense single paragraph keeps nearly every clause informative (limits, pricing, latency, caveats). It is on the long side and mixes operations, output, pricing and legal caveats in one unbroken block, but there is little pure filler.

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

Completeness5/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 not be explained, yet the description still summarizes them. Combined with error semantics, latency, pricing, free-tier limits, data provenance and a docs link, an agent has everything needed to decide and call correctly.

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, but the description goes further by describing what each input yields: a code returns one airport with runway and radio-frequency detail, while a name/city query returns up to 20 matches with name, codes, type, position, elevation, country, region and municipality. That output-linked semantics of code vs query exceeds the schema's terse constraints.

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 and resource ('Look up an airport') plus the accepted identifier forms (ICAO, IATA, name, ident). It explicitly names the sibling tool airport_distance as the one to use for a different task, so an agent can disambiguate without opening either schema.

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

Usage Guidelines5/5

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

Names the alternative (airport_distance) and the condition that selects it, and adds a hard usage boundary: 'Informational only: not for flight planning or navigation.' The code-vs-query selection is reinforced from the schema, and the country filter's condition ('optionally in one country') is stated.

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

Deploy Server