Burs-IA Utils

Buscar aeropuerto (IATA, ICAO o nombre)

airport-lookup

Read-onlyIdempotent

Busca un aeropuerto con servicio regular por código IATA, ICAO, ident de OurAirports o parte del nombre o ciudad (sin importar tildes) y devuelve códigos, coordenadas, altitud, tipo, municipio, país (ES/EN), región y zona horaria derivada, con datos OurAirports incluidos. Cuándo: hay que resolver un código (IATA, ICAO) o nombre de aeropuerto a sus códigos, coordenadas, país o zona horaria con fuente citada. No para: listar los aeropuertos de una ciudad o país (airport-search). 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: Finds one airport with scheduled service by IATA code, ICAO code, OurAirports ident or part of its name or city (accent-insensitive) and returns its codes, coordinates, elevation, type, municipality, country (ES/EN names), region and derived IANA time zone, from embedded… [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": {
      "query": "BOG"
    },
    "name": "airport-lookup"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	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
`lat`	No
`lon`	No
`iata`	No
`icao`	No
`name`	No
`type`	No
`ident`	No
`region`	No
`source`	No
`country`	No
`timezone`	No
`ambiguous`	No
`matched_by`	No
`elevation_m`	No
`elevation_ft`	No
`municipality`	No
`other_matches`	No
`country_name_en`	No
`country_name_es`	No
`scheduled_service`	No
`timezone_derived_from`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the description's 'sin efectos secundarios, sin red, sin estado guardado' largely restates them. It does add genuinely new behavior context: accent-insensitive matching, embedded OurAirports as the data source, determinism, and concrete limits (64 KB input, 1 s per call, 1 MB result). It does not say what happens when no airport matches, which is the main remaining gap for a single-result lookup.

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?

The purpose is front-loaded, then segmented into when / not-for / side effects / determinism / limits, which is easy to scan. The ES and EN text duplicate each other and the 'Efectos secundarios' sentence repeats the annotations, so a little of the length is not earning its place.

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?

An output schema exists, so return values need not be fully explained, yet the description still names the returned fields, the data source and the runtime limits — enough for a one-parameter lookup tool. What is missing is no-match behavior (error vs. empty) and whether an ambiguous city fragment errors or returns the single best match, which matters for this exact tool shape.

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% and the single 'query' parameter already documents the accepted formats and length bounds. The description adds meaning beyond the schema by specifying that name/city matching is partial and accent-insensitive, which tells the agent how the free-text form of the parameter behaves.

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 ('Busca un aeropuerto con servicio regular') plus the exact lookup keys accepted (IATA, ICAO, OurAirports ident, name/city fragment) and the returned fields. It explicitly contrasts itself with airport-search, so an agent can tell the two apart 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?

There is an explicit 'Cuándo' clause naming the trigger (resolving a code or name to codes, coordinates, country or time zone from a cited source) and an explicit 'No para' clause redirecting to airport-search for city/country listings. No inference is required to pick between the siblings.

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?