Skip to main content
Glama

Aeropuertos por ciudad, país o tipo

airport-search
Read-onlyIdempotent

Lista aeropuertos con servicio regular por ciudad o municipio (sin importar tildes), país (código ISO o nombre) y/o tipo (grande, mediano, pequeño), los mayores primero, con el total de coincidencias, con datos OurAirports incluidos. Cuándo: hay que listar los aeropuertos con servicio regular de una ciudad o país, o encontrar los mayores. No para: buscar un aeropuerto por código IATA o ICAO o por nombre (airport-lookup). 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: Lists airports with scheduled service by city or municipality (accent-insensitive), country (ISO code or name) and/or type (large, medium, small), largest first, with the total number of matches, from embedded OurAirports data. When: the airports with scheduled service of a city or country have to be listed, or the largest ones found. [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": {
      "city": "Medellín"
    },
    "name": "airport-search"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity or municipality name (Medellín, London) (string; optional; at least 2 chars; up to 100 chars).
typeNoAirport type (optional; one of: large_airport, medium_airport, small_airport).
limitNoMax results (integer; optional; default 10; min 1; max 25).
countryNoCountry: ISO 3166-1 alpha-2 (CO) or alpha-3 (COL) code, or name in English or Spanish (Colombia, Alemania, Germany) (string; optional; at least 1 chars; up to 80 chars).

Output Schema

NameRequiredDescriptionDefault
countNo
totalNo
sourceNo
countryNo
resultsNo
truncatedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld=false/idempotent/non-destructive, yet the description still adds real context: embedded OurAirports data, no network, no stored state, deterministic output, and concrete limits (64 KB input, 1 s per call, 1 MB result). The 'read-only' restatement is redundant with annotations, but the limits and determinism are information the annotations do not 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?

Well structured with labeled clauses (Cuándo / No para / Efectos secundarios / Determinista / Límites) and the core capability front-loaded. Slightly padded by a truncated bilingual 'EN' block that merely defers to inputSchema.description, which is duplication rather than added value.

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 four-parameter, all-optional, read-only filter tool with full schema coverage, an output schema, and rich annotations, nothing material is missing: filtering axes, ordering, total matches, determinism and size/time limits are all stated. Return-value detail is correctly omitted since an output schema exists.

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 the baseline is 3, but the description adds semantics the schema lacks: city matching is accent-insensitive, country accepts ISO alpha-2 or alpha-3 or a name in English or Spanish, and results are sorted largest-first with a total match count returned. Only 'limit' goes unmentioned in the description, which the schema documents fully.

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 ('Lista aeropuertos con servicio regular') plus the exact filter dimensions (city, country ISO/name, type) and the result ordering ('los mayores primero'). It also explicitly excludes the sibling case (lookup by IATA/ICAO/name -> airport-lookup), so an agent can distinguish it from airport-lookup, city-airports and airport-distance without opening any 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?

Provides an explicit 'Cuándo' clause naming the two triggering scenarios (list airports of a city/country, or find the largest) and an explicit 'No para' clause that routes code-based or name-based lookups to airport-lookup. There is no inference required to pick between this tool and its alternatives.

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.

Resources