ourairports-mcp-server

ourairports_search_runways

Read-onlyIdempotent

Search runways across the whole bundled OurAirports corpus by attribute, joined back to their airports — the cross-airport counterpart to ourairports_get_airport (which returns runways for one already-known airport). Filter by airport facets (country, region, type) and runway facets (surface, min_length_ft, min_width_ft, lighted). Returns one flat {airport, runway} row per matching runway, so an airport with three matching runways contributes three rows. surface is a case-insensitive substring match against the raw upstream surface string, not an exact code — the runway surface must CONTAIN your text, so a shorter fragment matches more variants (no controlled vocabulary: "asp" matches ASP, ASPH, and Asphalt). Lengths are the full runway surface, including displaced thresholds and overruns — not usable takeoff or landing distance; each runway also reports its displaced threshold per end. A runway whose length or width is unknown is excluded when the matching min_*ft filter is set — the data can never confirm it meets the threshold. Closed airports and closed runways are both excluded unless their include* flag is set. Use ourairports_list_countries for valid country/region codes. OurAirports is community-edited — not authoritative for flight operations.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Restrict to runways at airports of one type: large_airport, medium_airport, small_airport, heliport, seaplane_base, balloonport, or closed.
`limit`	No	Maximum runway rows to return (1–100). Defaults to OURAIRPORTS_DEFAULT_SEARCH_LIMIT (20).
`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.
`lighted`	No	Filter by runway lighting: true for lighted runways only, false for unlighted only. Omit to include both.
`surface`	No	Surface filter — case-insensitive substring match against the raw upstream surface string (free text, no controlled vocabulary; ~654 distinct values). Match the literal text as recorded: "asp" matches ASP/ASPH/Asphalt/ASPH-G, "con" matches CON/Concrete, "turf" or "grs" for grass strips. A shorter fragment matches more variants; there is no enum or reference tool for surfaces.
`min_width_ft`	No	Minimum runway width in feet (inclusive). Runways with an unknown width are excluded when this is set, never assumed to pass.
`min_length_ft`	No	Minimum length of the full runway surface in feet (inclusive), matched against lengthFt — which includes displaced thresholds and overruns, so this is not a usable-distance filter. Runways with an unknown length are excluded when this is set, never assumed to pass.
`include_closed_runways`	No	Include runways flagged closed. Off by default.
`include_closed_airports`	No	Include runways at airports of type "closed". Off by default.

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 runway rows returned. Present only when results were truncated.
`notice`	No	Guidance when nothing matched or results were capped — how to broaden or narrow.
`runways`	No	Matching runways, each paired with its airport. One row per runway — an airport with N matching runways contributes N rows.
`truncated`	No	Present and true only when more runways matched than were returned.
`totalCount`	No	Total matching runways before the limit was applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedSep 24, 2026

changedInput schema / properties / min_length_ft / description

Previous value: -"Minimum runway length in feet (inclusive). Runways with an unknown length are excluded when this is set, never assumed to pass."New value: +"Minimum length of the full runway surface in feet (inclusive), matched against lengthFt — which includes displaced thresholds and overruns, so this is not a usable-distance filter. Runways with an unknown length are excluded when this is set, never assumed to pass."

changedOutput schema / properties / runways / items / 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 / runways / items / properties / runway / description

Previous value: -"The matching runway — dimensions, surface, lighting, end designators, and headings."New value: +"The matching runway — full-surface dimensions, surface, lighting, and per-end designators, headings, and displaced thresholds."

addedOutput schema / properties / runways / items / properties / runway / 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 / runway / 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 / runway / 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 / properties / runway / 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"
+]

Changed36 schema fields changedSep 19, 2026
- removedOutput schema / properties / runways / items / properties / airport / properties / continent / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / continent / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / countryName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / countryName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / elevationFt / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / elevationFt / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / gpsCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / gpsCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / iataCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / iataCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / icaoCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / icaoCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / isoCountry / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / isoCountry / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / isoRegion / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / isoRegion / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / localCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / localCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / municipality / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / municipality / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / airport / properties / regionName / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / airport / properties / regionName / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / runway / properties / heHeadingDegT / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / runway / properties / heHeadingDegT / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / runway / properties / heIdent / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / runway / properties / heIdent / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / runway / properties / leHeadingDegT / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / runway / properties / leHeadingDegT / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / runway / properties / leIdent / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / runway / properties / leIdent / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / runway / properties / lengthFt / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / runway / properties / lengthFt / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / runway / properties / surface / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / runway / properties / surface / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / runways / items / properties / runway / properties / widthFt / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / runways / items / properties / runway / 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": [
+      "runways",
+      "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: -[
-  "runways",
-  "totalCount"
-]

AddedJul 18, 2026

TDQS

A5/5.0

Behavior5/5

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

Annotations indicate read-only, idempotent, closed-world behavior, and the description adds rich context beyond them: it explains that surface is a case-insensitive substring match with examples ('asp' matches ASP/ASPH/Asphalt), that length includes displaced thresholds/overruns and is not usable distance, that unknown lengths/widths cause exclusion when min filters are set, and that closed airports/runways are excluded unless flags are set. It also discloses the flat row structure (one row per matching runway). These are critical operational details not present in the annotations.

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?

The description is long but every sentence carries essential information. It is front-loaded with the core purpose, then differentiates from a sibling, then explains filtering capabilities, output format, and specific field semantics. There is no redundancy; the structure guides the agent from high-level intent to low-level constraints in a logical flow. Given the tool's complexity (10 parameters, many nuances), this length is justified and well-organized.

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 presence of an output schema (context signal) and comprehensive parameter descriptions in both schema and tool description, nothing crucial is missing. The description covers the scope, filtering options, exclusions, return-shape behavior, and caveats about data quality ('community-edited — not authoritative'). The agent has all the information needed to correctly invoke the tool and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (every parameter has a schema description), but the tool description goes well beyond that. For example, it clarifies that 'surface' is a free-text substring match and gives concrete match examples; it explains that min_length_ft is not a usable-distance filter and that unknown values are excluded; it details the limit default and behavior. This adds operational meaning that the schema alone does not provide, so it fully compensates and exceeds the baseline.

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 opens with a specific verb and resource: 'Search runways across the whole bundled OurAirports corpus by attribute, joined back to their airports.' It clearly differentiates from ourairports_get_airport by calling itself 'the cross-airport counterpart' that searches across all airports, whereas the sibling returns runways for one known airport. Scope, resource, and differentiation are all explicit.

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?

Usage is guided precisely: the description names the sibling alternative (ourairports_get_airport) and states when this tool is appropriate (searching across the corpus) versus when the sibling is used (one already-known airport). It also points the agent to ourairports_list_countries for valid country/region codes, giving concrete next steps for correct invocation.

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.