ourairports-mcp-server

ourairports_get_airport

Read-onlyIdempotent

Fetch the full record for one airport resolved by ANY code — IATA (SEA), ICAO (KSEA), GPS, national/local, or the OurAirports ident — with its runways and radio frequencies inline. The single code param is resolved case-insensitively across all five identifier spaces (priority: ident, then ICAO, IATA, GPS, local). The response always echoes the airport's complete code set and a resolutionNote naming which space matched; when other airports carry the same code, the note names each one (ident, country, code space) and why this airport won, so a wrong resolution is self-correcting — pass the other airport's ident to fetch it. Absent codes are reported as null, never an error. Runway lengths are the full runway surface (displaced thresholds and overruns included), not usable takeoff or landing distance. Closed airports always resolve. OurAirports is community-edited — not authoritative for flight operations.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	Any airport code: IATA (SEA), ICAO (KSEA), GPS code, national/local code, or the OurAirports ident. Case-insensitive; surrounding whitespace is ignored.
`include`	No	Which related records to include inline. Defaults to both. Pass a subset to trim the response.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`airport`	No	The resolved airport record. Codes the airport lacks are null.
`runways`	No	Runways for the airport. Empty when the airport has none OR when `runways` was not in `include` — check `included` to tell which.
`included`	No	Which related-record sets this response carries, echoing the effective `include` selection. A relation NOT listed here was omitted by `include` (its array is empty for that reason); a listed relation with an empty array genuinely has no records.
`frequencies`	No	Radio frequencies in MHz. Empty when the airport has none OR when `frequencies` was not in `include` — check `included` to tell which.
`resolvedVia`	No	Which identifier space the code matched: ident, icao_code, iata_code, gps_code, or local_code.
`resolutionNote`	No	How the code resolved: the identifier space that matched and, when other airports carry the same code, why this one won (resolution priority or dataset row order) and each other airport's ident, country, and code space — pass that ident to fetch it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 24, 2026

changedOutput schema / properties / airport / properties / icaoCode / description

Previous value: -"4-letter ICAO code, or null when the airport has none (~85% of fields)."New value: +"4-letter ICAO code, or null when the airport has none (~88% of fields)."

changedOutput schema / properties / resolutionNote / description

Previous value: -"Human-readable note on how the code resolved, including an ambiguity warning for shared national codes."New value: +"How the code resolved: the identifier space that matched and, when other airports carry the same code, why this one won (resolution priority or dataset row order) and each other airport's ident, country, and code space — pass that ident to fetch it."

changedOutput schema / properties / runways / items / description

Previous value: -"A runway with dimensions, surface, lighting, and end designators/headings."New value: +"A runway with full-surface dimensions, surface, lighting, and per-end designators, headings, and displaced thresholds."

addedOutput schema / properties / runways / items / properties / heDisplacedThresholdFt

Added value: +{
+  "description": "Length of the displaced threshold at the high end (heIdent) in feet — part of lengthFt. Null when none is recorded.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

addedOutput schema / properties / runways / items / properties / leDisplacedThresholdFt

Added value: +{
+  "description": "Length of the displaced threshold at the low end (leIdent) in feet — part of lengthFt. Null when none is recorded.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

changedOutput schema / properties / runways / items / properties / lengthFt / description

Previous value: -"Runway length in feet, or null when unknown."New value: +"Length of the full runway surface in feet, including displaced thresholds and overrun areas — not the usable takeoff or landing distance. Null when unknown."

changedOutput schema / properties / runways / items / required

Previous value: -[
-  "id",
-  "lengthFt",
-  "widthFt",
-  "surface",
-  "lighted",
-  "closed",
-  "leIdent",
-  "leHeadingDegT",
-  "heIdent",
-  "heHeadingDegT"
-]New value: +[
+  "id",
+  "lengthFt",
+  "widthFt",
+  "surface",
+  "lighted",
+  "closed",
+  "leIdent",
+  "leHeadingDegT",
+  "leDisplacedThresholdFt",
+  "heIdent",
+  "heHeadingDegT",
+  "heDisplacedThresholdFt"
+]

Changed40 schema fields changedSep 19, 2026
- removedOutput schema / properties / airport / properties / continent / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / continent / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / countryName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / countryName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / elevationFt / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / elevationFt / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / gpsCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / gpsCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / iataCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / iataCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / icaoCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / icaoCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / isoCountry / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / isoCountry / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / isoRegion / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / isoRegion / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / localCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / localCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / municipality / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / municipality / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airport / properties / regionName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airport / properties / regionName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / frequencies / items / properties / description / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / frequencies / items / properties / description / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / frequencies / items / properties / frequencyMhz / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / frequencies / items / properties / frequencyMhz / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / heHeadingDegT / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / heHeadingDegT / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / heIdent / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / heIdent / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / leHeadingDegT / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / leHeadingDegT / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / leIdent / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / leIdent / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / lengthFt / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / lengthFt / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / surface / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / surface / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / widthFt / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / widthFt / type
```
Added value: +[
+  "number",
+  "null"
+]
```

Changed6 schema fields changedAug 25, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

addedOutput schema / anyOf

Added value: +[
+  {
+    "not": {
+      "required": [
+        "error"
+      ]
+    },
+    "required": [
+      "airport",
+      "resolvedVia",
+      "resolutionNote",
+      "included",
+      "runways",
+      "frequencies"
+    ]
+  },
+  {
+    "required": [
+      "error"
+    ]
+  }
+]

addedOutput schema / properties / error

Added value: +{
+  "additionalProperties": {},
+  "description": "Present when the call failed. Absent on success.",
+  "properties": {
+    "code": {
+      "description": "JSON-RPC error code for this failure.",
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "data": {
+      "additionalProperties": {},
+      "properties": {
+        "reason": {
+          "description": "Machine-readable failure mode. Declared by this tool: `unknown_code`: No airport matched the supplied code in any identifier space (IATA/ICAO/GPS/local/ident). Other values are possible when a failure originates below the handler.",
+          "examples": [
+            "unknown_code"
+          ],
+          "type": "string"
+        },
+        "recovery": {
+          "additionalProperties": {},
+          "description": "Actionable next step for the caller.",
+          "properties": {
+            "hint": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "hint"
+          ],
+          "type": "object"
+        },
+        "retryable": {
+          "description": "Whether retrying may succeed.",
+          "type": "boolean"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable description of what went wrong.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "code",
+    "message"
+  ],
+  "type": "object"
+}

removedOutput schema / required

Removed value: -[
-  "airport",
-  "resolvedVia",
-  "resolutionNote",
-  "included",
-  "runways",
-  "frequencies"
-]

Changed5 schema fields changedJul 18, 2026

changedInput schema / properties / code / description

Previous value: -"Any airport code: IATA (SEA), ICAO (KSEA), GPS code, national/local code, or the OurAirports ident. Case-insensitive."New value: +"Any airport code: IATA (SEA), ICAO (KSEA), GPS code, national/local code, or the OurAirports ident. Case-insensitive; surrounding whitespace is ignored."

changedOutput schema / properties / frequencies / description

Previous value: -"Radio frequencies in MHz (empty array when none recorded, or when frequencies were not requested in `include`)."New value: +"Radio frequencies in MHz. Empty when the airport has none OR when `frequencies` was not in `include` — check `included` to tell which."

addedOutput schema / properties / included

Added value: +{
+  "description": "Which related-record sets this response carries, echoing the effective `include` selection. A relation NOT listed here was omitted by `include` (its array is empty for that reason); a listed relation with an empty array genuinely has no records.",
+  "items": {
+    "enum": [
+      "runways",
+      "frequencies"
+    ],
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / runways / description

Previous value: -"Runways for the airport (empty array when none recorded, or when runways were not requested in `include`)."New value: +"Runways for the airport. Empty when the airport has none OR when `runways` was not in `include` — check `included` to tell which."

changedOutput schema / required

Previous value: -[
-  "airport",
-  "resolvedVia",
-  "resolutionNote",
-  "runways",
-  "frequencies"
-]New value: +[
+  "airport",
+  "resolvedVia",
+  "resolutionNote",
+  "included",
+  "runways",
+  "frequencies"
+]

First observedJun 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses resolution priority, case-insensitive matching, null-on-absent behavior rather than errors, runway length semantics, closed-airport resolution, and the community-edited reliability caveat. This is substantial behavioral context that annotations alone would not provide.

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

Conciseness5/5

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

Although longer than average, every sentence carries distinct operational value: resolution scope, priority, self-correcting notes, null behavior, runway measurement caveats, and data quality. The description is front-loaded with the primary purpose and then layers essential caveats without redundancy.

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?

Given the output schema exists, return-value details do not need repeating. The description covers ambiguous resolutions, error semantics, runway interpretation, closed airports, and authority limitations, so an agent has enough context to call the tool correctly and interpret unusual results.

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. The description adds real meaning beyond the schema by explaining code resolution priority, the resolutionNote self-correction mechanism, and null handling for absent codes. The include parameter is adequately covered by both schema and the inline/trim prose, but the extra semantic value is mostly for the code parameter.

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 names a specific verb and resource ('Fetch the full record for one airport') and scopes it precisely with 'resolved by ANY code'. It also distinguishes itself from search/find siblings by emphasizing exact single-record resolution across identifier spaces and inline runways/frequencies.

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?

The description gives clear context: use this when you have any airport code and want a single resolved record with related data. It does not explicitly name sibling alternatives or state when to prefer search/find, but the exact-code-resolution framing makes the intended use unambiguous.

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

All ourairports-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.