airportsAirport directory — name, IATA/ICAO codes, country, GPS, timezone.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| search | No | Free-text — name / city | |
| iata_code | No | 3-letter IATA code | |
| icao_code | No | 4-letter ICAO code | |
| country_iso2 | No | ISO 3166-1 alpha-2 country |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Array of airport objects | |
| pagination | No | Pagination metadata |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / properties / data / items / properties / phone_number / descriptionAdded value: +"Airport phone number, null when unknown. Declared null-only until 2026-08-13 — a one-sample inference artifact, not the real type."Output schema / properties / data / items / properties / phone_number / typePrevious value: -"null"New value: +[
+ "string",
+ "null"
+]Output schema / properties / data / items / properties / airport_idAdded value: +{
+ "type": "string"
+}Output schema / properties / data / items / properties / city_nameRemoved value: -{
- "description": "City name",
- "type": "string"
-}Output schema / properties / data / items / properties / country_name / typePrevious value: -"string"New value: +[
+ "string",
+ "null"
+]Output schema / properties / data / items / properties / geoname_idAdded value: +{
+ "type": "string"
+}Output schema / properties / data / items / properties / gmt_offset_secondsRemoved value: -{
- "description": "GMT offset in seconds",
- "type": "number"
-}Output schema / properties / data / items / properties / idAdded value: +{
+ "type": "string"
+}Output schema / properties / data / items / properties / latitude / typePrevious value: -"number"New value: +"string"Output schema / properties / data / items / properties / longitude / typePrevious value: -"number"New value: +"string"Output schema / properties / data / items / properties / phone_numberAdded value: +{
+ "type": "null"
+}Output schema / properties / pagination / properties / totalAdded value: +{
+ "type": "number"
+}Input schema / examplesAdded value: +[
+ {
+ "iata_code": "JFK"
+ },
+ {
+ "country_iso2": "GB",
+ "search": "London"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "data": {
+ "description": "Array of airport objects",
+ "items": {
+ "properties": {
+ "airport_name": {
+ "description": "Full airport name",
+ "type": "string"
+ },
+ "city_iata_code": {
+ "description": "City IATA code",
+ "type": "string"
+ },
+ "city_name": {
+ "description": "City name",
+ "type": "string"
+ },
+ "country_iso2": {
+ "description": "ISO 3166-1 alpha-2 country code",
+ "type": "string"
+ },
+ "country_name": {
+ "description": "Country name",
+ "type": "string"
+ },
+ "gmt": {
+ "description": "GMT offset",
+ "type": "string"
+ },
+ "gmt_offset_seconds": {
+ "description": "GMT offset in seconds",
+ "type": "number"
+ },
+ "iata_code": {
+ "description": "3-letter IATA code",
+ "type": "string"
+ },
+ "icao_code": {
+ "description": "4-letter ICAO code",
+ "type": "string"
+ },
+ "latitude": {
+ "description": "Latitude coordinate",
+ "type": "number"
+ },
+ "longitude": {
+ "description": "Longitude coordinate",
+ "type": "number"
+ },
+ "timezone": {
+ "description": "IANA timezone",
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "pagination": {
+ "description": "Pagination metadata",
+ "properties": {
+ "count": {
+ "type": "number"
+ },
+ "limit": {
+ "type": "number"
+ },
+ "offset": {
+ "type": "number"
+ }
+ },
+ "type": "object"
+ }
+ },
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds the list of returned fields (name, codes, country, GPS, timezone), which is modest context but not required for behavior. No contradiction.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, compact sentence that front-loads the purpose. No wasted words, though it could be slightly more informative; it's appropriately concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple directory lookup with good annotations, the description is adequate but minimal. It doesn't explicitly say that you can search/list airports or how the parameters relate to the output fields. The schema examples compensate, but the description alone leaves some ambiguity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema descriptions cover search, iata_code, icao_code, and country_iso2, but limit and offset lack descriptions. The description mentions output fields but does not explain how to use the parameters or paginate. With 67% coverage, the description does little to compensate for the missing parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description identifies the tool as an airport directory and lists the key data fields (name, IATA/ICAO codes, country, GPS, timezone), making its purpose clear. It distinguishes from sibling tools like airlines, cities, and countries. However, it lacks an explicit verb (e.g., 'search' or 'list'), so it's a 4 rather than 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It doesn't mention filtering by code, country, or name, nor any exclusions or prerequisites. The schema examples hint at usage, but the description itself offers no direct guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Many tools have overlapping purposes, such as ask_pipeworx, ask_pipeworx_beta, and deep_research all routing queries, and the polymarket family (arbitrage, edges, edge_tracker, fill_risk) covering similar ground. While descriptions are detailed, an agent could easily select the wrong tool.
Tool names mix bare nouns (airlines, airports, flights) with verb phrases (compare_entities, resolve_entity) and standalone verbs (remember, forget), with no consistent verb_noun pattern. Names like ask_pipeworx_beta and scan_competitor_ai_presence are internally inconsistent with the rest.
37 tools is far beyond the typical scope for a single server, and many are unrelated to the aviation theme, suggesting a lack of focus. The core aviation functionality only accounts for 6 of the tools.
The aviation tools (airlines, airports, flights, routes, cities, countries) cover basic lookups, but advanced operations like delay statistics or aircraft data are absent. The unrelated tools do not fill these gaps, and the overall surface feels shallow for a server claiming to be an Aviationstack.