Tanod MCP Server (Deprecated)

by dev.tanod

Overview Discussions Admin

This connector has been deprecated

The correct URL is https://tanod.dev/mcp and NOT https://tanod.dev/mcp/ (CORRECT: NO TRAILING SLASH)

Correct Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod

WRONG Glama listing: https://glama.ai/mcp/connectors/dev.tanod/tanod-mcp-server/

skypeek: look up an airport

lookup_airport

Read-onlyIdempotent

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. 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

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

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.

Changed8 schema fields changedNov 3, 2026
- addedOutput schema / properties / airports / items / properties / continent
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / airports / items / properties / elevation_ft
```
Added value: +{
+  "type": [
+    "number",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / airports / items / properties / elevation_m
```
Added value: +{
+  "type": [
+    "integer",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / airports / items / properties / gps_code
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / airports / items / properties / local_code
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / airports / items / properties / region
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / airports / items / properties / scheduled_service
```
Added value: +{
+  "type": [
+    "boolean",
+    "null"
+  ]
+}
```
- addedOutput schema / properties / airports / items / properties / wikipedia
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```
First observedOct 22, 2026

TDQS

A4.4/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real value beyond them: bundled local data with no upstream call, a 404 airport_not_found (unbilled) for unknown codes, latency expectations, and pricing/free-tier limits. However, the blanket openWorldHint=true sits slightly at odds with 'answered from a bundled copy (no upstream call)', and the return shape is only loosely sketched despite an output schema existing.

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?

Front-loaded with purpose and the sibling alternative, and every clause carries information (data source, error semantics, latency, price). It is dense but slightly run-on, with licensing/boilerplate tail matter that an agent rarely needs before calling.

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?

For a read-only lookup with a full schema and an output schema, the description covers inputs, alternatives, failure mode, cost, and performance. Nothing an agent needs to select or invoke it correctly is missing.

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 description coverage is 100%, so the baseline is 3, but the description adds meaning the schema does not: code and query are alternatives ('or by name', 'optionally in one country'), and up to 20 name/city matches confirms the limit ceiling's intent. It stops short of explaining precedence if both code and query are sent.

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 (look up an airport) and enumerates the lookup keys (ICAO, IATA, ident, name, city). It explicitly names the sibling airport_distance as the tool for a different task, so an agent can disambiguate without opening a 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?

Gives an explicit alternative ('For the distance between two use airport_distance') plus an explicit exclusion ('Informational only: not for flight planning or navigation'). It also covers country-filtered name search and the code-vs-query split, leaving little to inference.

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

All Tanod MCP Server (Deprecated) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?