Skip to main content
Glama

Aviation & Space Weather Data (Tanod)

airport_distance

Read-onlyIdempotent

skypeek: Calculate the great-circle distance between two airports or points. For airport details use lookup_airport. Returns the great-circle distance between two airports (by code) or coordinates, in km, nautical miles and statute miles, with the initial and final true bearings and the midpoint. Input: from and to: each an airport code or {lat, lon}. Informational only: not for flight planning or navigation. A spherical (haversine) distance, within about 0.5 % of the WGS-84 geodesic. Airports: OurAirports (public domain); the data may contain errors and no endorsement is implied. An unknown code is a 422 unknown_airport (not charged). Typically under 0.1 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

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": {
      "from": "<from>",
      "to": "<to>"
    },
    "name": "airport_distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesAirport code (ICAO, IATA or ident) or {lat, lon}.
fromYesAirport code (ICAO, IATA or ident) or {lat, lon}.

Output Schema

NameRequiredDescriptionDefault
toNo
fromNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
methodNo
sourceNo
midpointNo
disclaimerNo
distance_kmNo
distance_miNo
distance_nmNo
final_bearing_degNo
initial_bearing_degNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • removedInput schema / $defs / LatLon / properties / lat / title
      Removed value: -"Lat"
    • removedInput schema / $defs / LatLon / properties / lon / title
      Removed value: -"Lon"
    • removedInput schema / $defs / LatLon / title
      Removed value: -"LatLon"
    • removedInput schema / properties / from / title
      Removed value: -"From"
    • removedInput schema / properties / to / title
      Removed value: -"To"
    • removedInput schema / title
      Removed value: -"airport_distanceArguments"
    • removedOutput schema / properties / source / properties
      Removed value: -{
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "name": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "notice": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "terms": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "url": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "disclaimer": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "distance_km": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "distance_mi": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "distance_nm": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "final_bearing_deg": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "from": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "initial_bearing_deg": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "method": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "midpoint": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "source": {
      +      "properties": {
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "name": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "notice": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "terms": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "url": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "to": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/openWorld annotations, the description discloses error behavior (422 unknown_airport, not charged), latency (<0.1 s), price and free-tier limits, data provenance, and the ~0.5% accuracy bound versus the WGS-84 geodesic. This is exactly the kind of operational context annotations cannot carry.

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?

Core purpose, alternative, and output shape are front-loaded, and most sentences carry real information. The licensing/disclaimer sentence ('OurAirports (public domain); the data may contain errors and no endorsement is implied') and the docs URL are boilerplate that an agent gains little from.

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 two-parameter, idempotent geometry lookup, the description covers the model used, expected accuracy, error case, latency, and cost. Even though an output schema exists, it also summarizes the return values (distance units, bearings, midpoint), leaving nothing critical unstated.

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% and the schema already documents that each of `from`/`to` accepts an ICAO/IATA/ident code or a {lat, lon} object with ranges. The description repeats this fact without adding format examples, mixing rules, or other semantics, so the 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?

The description opens with a specific verb and resource ('Calculate the great-circle distance between two airports or points') and immediately distinguishes itself from the sibling lookup_airport, which handles details rather than distance.

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?

It names the alternative for a related need ('For airport details use lookup_airport') and states an explicit exclusion ('not for flight planning or navigation'). The agent knows both when to call it and when not to.

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.