ourairports-mcp-server

ourairports_search_airports

Read-onlyIdempotent

Search the bundled OurAirports corpus by free-text (name / municipality / keywords) and/or facets (country, region, type). Every query token must match (word order and partial words are handled). Returns ranked airport summaries — operational and larger airports first — each with its full code set and coordinates, ready to chain into ourairports_get_airport. Closed airports are excluded unless include_closed is set. Use ourairports_list_countries for valid country/region codes. For "nearest airport to a coordinate" use ourairports_find_airports instead. OurAirports is community-edited — not authoritative for flight operations.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Restrict to one airport type: large_airport, medium_airport, small_airport, heliport, seaplane_base, balloonport, or closed.
`limit`	No	Maximum airports to return (1–100). Defaults to OURAIRPORTS_DEFAULT_SEARCH_LIMIT (20).
`query`	No	Free-text search over airport name, municipality, and keywords. Tokens are AND-matched. Omit to browse purely by facets.
`region`	No	ISO 3166-2 region code filter (e.g. US-WA). Exact match, case-insensitive; surrounding whitespace is ignored.
`country`	No	ISO 3166-1 alpha-2 country code filter (e.g. US). Exact match, case-insensitive; surrounding whitespace is ignored. Discover codes with ourairports_list_countries.
`include_closed`	No	Include airports of type "closed". Off by default — closed airports pollute the live-flight grounding use case.

Output Schema

TableJSON Schema

Name	Required	Description
`cap`	No	The limit that was applied. Present only when results were truncated.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of airports returned. Present only when results were truncated.
`notice`	No	Guidance when nothing matched or results were capped — how to broaden or narrow.
`airports`	No	Matching airports, ranked best-first. Codes the airport lacks are null.
`truncated`	No	Present and true only when more airports matched than were returned.
`totalCount`	No	Total airports matched before the limit was applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / properties / airports / items / 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)."

Changed22 schema fields changedSep 19, 2026
- removedOutput schema / properties / airports / items / properties / continent / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / continent / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / countryName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / countryName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / elevationFt / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / elevationFt / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / gpsCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / gpsCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / iataCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / iataCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / icaoCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / icaoCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / isoCountry / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / isoCountry / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / isoRegion / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / isoRegion / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / localCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / localCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / municipality / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / municipality / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / airports / items / properties / regionName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / airports / items / properties / regionName / type
```
Added value: +[
+  "string",
+  "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": [
+      "airports",
+      "totalCount"
+    ]
+  },
+  {
+    "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.",
+          "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: -[
-  "airports",
-  "totalCount"
-]

Changed4 schema fields changedJul 18, 2026

changedInput schema / properties / country / description

Previous value: -"ISO 3166-1 alpha-2 country code filter (e.g. US). Exact match. Discover codes with ourairports_list_countries."New value: +"ISO 3166-1 alpha-2 country code filter (e.g. US). Exact match, case-insensitive; surrounding whitespace is ignored. Discover codes with ourairports_list_countries."

addedInput schema / properties / country / minLength
```
Added value: +1
```

changedInput schema / properties / region / description

Previous value: -"ISO 3166-2 region code filter (e.g. US-WA). Exact match."New value: +"ISO 3166-2 region code filter (e.g. US-WA). Exact match, case-insensitive; surrounding whitespace is ignored."

addedInput schema / properties / region / minLength
```
Added value: +1
```

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 annotations (readOnlyHint, idempotentHint), it discloses token matching semantics, exclusion of closed airports by default, ranking behavior, and a data-quality caveat ('community-edited — not authoritative'). No contradiction with annotations; adds substantial behavioral context.

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?

Three well-structured sentences: purpose first, then matching behavior and ranking, then usage guidance and caveat. Every sentence adds value; no filler or 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?

With a full parameter schema and output schema present, the description covers usage boundaries, alternative tools, data caveats, and exclusion logic. Nothing an agent needs to call it correctly is missing.

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 coverage is 100% and each parameter already has a clear description. The description reinforces query token behavior and the rationale for include_closed, but adds little parameter-specific meaning beyond the schema, so baseline 3 applies.

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 ('Search') and resource ('bundled OurAirports corpus'), and clarifies scope (free-text and/or facets). It names the sibling it is not ('use ourairports_find_airports for nearest coordinate') and shows chaining to get_airport, so an agent can distinguish it clearly.

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?

Explicitly states when to use the tool, gives a concrete alternative for a different use case (nearest airport), advises using list_countries for valid codes, and notes the include_closed exception. This is complete routing guidance.

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.