Burs-IA Utils

Distancia y rumbo entre dos aeropuertos

airport-distance

Read-onlyIdempotent

Calcula la distancia ortodrómica (km, millas náuticas, millas) y el rumbo inicial entre dos aeropuertos dados por IATA, ICAO o nombre, más una estimación modelada de tiempo de vuelo (800 km/h + 30 min), con la lista OurAirports incluida. Cuándo: se necesita la distancia ortodrómica, el rumbo o un tiempo de vuelo aproximado entre dos aeropuertos. No para: calcular la distancia ortodrómica (city-distance). Efectos secundarios: ninguno (solo lectura, sin red, sin estado guardado). Determinista: la misma entrada da la misma salida. Límites: entrada JSON de hasta 64 KB, 1 s por llamada, resultado de hasta 1 MB.

EN: Computes the great-circle distance (km, nautical miles, miles) and initial bearing between two airports given by IATA, ICAO or name, plus a modelled flight-time estimate (800 km/h cruise + 30 min), each airport resolved in the embedded OurAirports list. When: the great-circle distance, bearing or a rough flight time between two airports is needed. [EN completo / full EN: inputSchema.description]

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "MDE",
      "from": "BOG"
    },
    "name": "airport-distance"
  }
}

Input Schema

Name	Required	Description	Default
`to`	Yes	Destination airport: IATA code (BOG), ICAO code (SKBO), OurAirports ident, or part of the airport name or city (El Dorado, Medellín) (string; required; at least 2 chars; up to 100 chars).
`from`	Yes	Origin airport: IATA code (BOG), ICAO code (SKBO), OurAirports ident, or part of the airport name or city (El Dorado, Medellín) (string; required; at least 2 chars; up to 100 chars).

Output Schema

Name	Required	Description	Default
`to`	No
`from`	No
`notes`	No
`method`	No
`source`	No
`compass`	No
`ambiguous`	No
`distance_km`	No
`distance_mi`	No
`distance_nmi`	No
`other_matches`	No
`initial_bearing`	No
`flight_time_estimate_h`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint=false, idempotentHint and destructiveHint=false, so 'solo lectura, sin red, sin estado guardado' is largely restating them. Beyond that, the description adds genuinely useful behavior: the embedded OurAirports resolution list, the flight-time model (800 km/h cruise + 30 min), determinism, and concrete limits of 64 KB input, 1 s per call and 1 MB result.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The labelled structure (When / Not for / Side effects / Deterministic / Limits) is easy to scan and the key purpose is front-loaded. However the entire text is duplicated in Spanish and English, roughly doubling length with no new information, and the same content is repeated again inside inputSchema.description.

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 read-only calculation tool with full schema coverage and an output schema, nothing essential is missing: inputs, resolution source, computational model, determinism, side effects and resource limits are all covered.

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 description coverage is 100% and both parameters already document accepted forms (IATA, ICAO, ident, name/city fragment) plus length bounds, so the description adds no parameter-level detail beyond the schema. The only extra signal, that resolution happens against the embedded OurAirports list, is marginal for callers.

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 set: great-circle distance, initial bearing and modelled flight time between two airports resolved from IATA/ICAO/name/OurAirports ident. It names the sibling it is not (city-distance) and the embedded OurAirports dataset, so an agent can distinguish it from airport-lookup, airport-search and geo-haversine 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 Guidelines4/5

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

Explicit 'Cuándo/When' and 'No para/Not for' clauses give both positive and negative routing, and point at city-distance as the alternative. The negative clause is slightly awkward because it is phrased as the very function this tool performs ('no para: calcular la distancia ortodrómica'), which only the parenthetical sibling name disambiguates.

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

All Burs-IA Utils tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?