ourairports-mcp-server

ourairports_find_airports

Read-onlyIdempotent

Find airports within a radius of a latitude/longitude, ranked nearest-first by great-circle distance, each with its distance (km) and bearing (degrees true) from the query point. The grounding tool for "nearest airport to here" — pair it with a live aviation server to fetch weather or positions for the result. Takes a coordinate only: no geocoding, so resolve place names to lat/lon upstream first (e.g. an OpenStreetMap or Open-Meteo geocode tool). Closed airports are excluded unless include_closed is set. totalCount is the in-radius match count before limit; a capped result says so. OurAirports is community-edited — not authoritative for flight operations.

Input Schema

TableJSON Schema

Name	Required	Description
`type`	No	Restrict to one airport type (e.g. large_airport for major fields only).
`limit`	No	Maximum airports to return (1–50). Defaults to OURAIRPORTS_DEFAULT_SEARCH_LIMIT (20).
`latitude`	Yes	Query point latitude in decimal degrees (WGS84), −90 to 90.
`longitude`	Yes	Query point longitude in decimal degrees (WGS84), −180 to 180.
`radius_km`	No	Search radius in kilometers (1–500). Defaults to 100.
`include_closed`	No	Include 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 airports returned. Present only when results were truncated.
`notice`	No	Guidance when no airport fell within the radius or results were capped — how to widen or narrow.
`airports`	No	Airports within the radius, nearest-first.
`truncated`	No	Present and true only when more airports matched than were returned.
`totalCount`	No	Airports within the radius that pass the type and include_closed filters, counted before the limit was applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 24, 2026

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

addedOutput schema / properties / cap

Added value: +{
+  "description": "The limit that was applied. Present only when results were truncated.",
+  "type": "number"
+}

changedOutput schema / properties / notice / description

Previous value: -"Guidance when no airport fell within the radius — e.g. widen radius_km."New value: +"Guidance when no airport fell within the radius or results were capped — how to widen or narrow."

addedOutput schema / properties / shown

Added value: +{
+  "description": "Number of airports returned. Present only when results were truncated.",
+  "type": "number"
+}

changedOutput schema / properties / totalCount / description

Previous value: -"Number of airports returned within the radius."New value: +"Airports within the radius that pass the type and include_closed filters, counted before the limit was applied."

addedOutput schema / properties / truncated

Added value: +{
+  "description": "Present and true only when more airports matched than were returned.",
+  "type": "boolean"
+}

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

Changed2 schema fields changedJun 30, 2026

removedInput schema / properties / limit / default
```
Removed value: -10
```

changedInput schema / properties / limit / description

Previous value: -"Maximum airports to return (1–50). Defaults to 10."New value: +"Maximum airports to return (1–50). Defaults to OURAIRPORTS_DEFAULT_SEARCH_LIMIT (20)."

First observedJun 16, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and idempotentHint, but the description goes well beyond: it discloses the output fields (distance km, bearing degrees true), the default exclusion of closed airports, the meaning of totalCount before limit, the fact that a capped result says so, and the community-edited nature of the data source. This is extensive behavioral disclosure that materially helps an agent reason about consequences, especially the non-authoritative caveat.

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?

The description is about 120 words, which is longer than typical but every sentence earns its place: purpose, ranking, output, usage suggestion, no-geocoding caveat, closed-airport default, totalCount semantics, and data-quality warning. It is front-loaded with the core function and then adds contextual detail. Slightly verbose but not bloated; the structure is logical and scannable. A 4 reflects good but not perfectly lean writing.

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 tool with six parameters, an output schema, and annotations, the description covers all critical aspects an agent needs: the query model (radius around a point), output content (distance, bearing), edge cases (closed airports, capped results, totalCount), external dependencies (no geocoding), and data reliability (community-edited). Nothing essential is missing, and it even anticipates the need to combine with other tools. This is complete for the tool's complexity.

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 covers 100% of parameters with descriptions, so the baseline is 3. The description adds value by clarifying that the tool takes a coordinate only and does not geocode, implicitly telling the agent that latitude/longitude must be in WGS84 decimal degrees (already in schema) and that place names must be resolved upstream. It also explains the default for limit via env var and the include_closed behavior. These additions go beyond mere restatement, earning a 4.

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–resource pair: 'Find airports within a radius of a latitude/longitude, ranked nearest-first by great-circle distance'. It clearly states the core behavior and distinguishes itself from siblings like search_airports or get_airport by focusing on radius-based proximity search with distance and bearing output. The phrasing leaves no ambiguity about what the tool does.

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 actionable usage context: it calls itself 'the grounding tool for nearest airport to here' and advises pairing with a live aviation server for weather/positions, and resolving place names upstream via geocoding tools. While it does not explicitly say 'use this instead of search_airports', the radius-vs-search distinction is implicit. The closed-airport exclusion and totalCount semantics further guide correct invocation. Missing an explicit when-not-to-use, but the guidance is strong overall.

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.