FlightDB

Flight_search_airports

Read-only

Search airports by name, city, IATA or ICAO code. Returns large and medium airports only. Use this to find an airport's ICAO code before calling other airport tools.

Input Schema

Name	Required	Description	Default
`q`	Yes
`limit`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedOct 24, 2026
- removedOutput schema / properties / data / items / properties / elevation_ft / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / elevation_ft / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / gps_code / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / gps_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / home_link / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / home_link / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / iata_code / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / iata_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / keywords / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / keywords / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / local_code / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / local_code / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / municipality / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / municipality / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / items / properties / wikipedia_link / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / items / properties / wikipedia_link / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With readOnlyHint, openWorldHint=false, and destructiveHint=false already present, the description adds useful behavioral context by stating that only large and medium airports are returned. It does not need to repeat the safety annotations, and it introduces 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.

Conciseness5/5

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

The description is three short, front-loaded sentences with no wasted text. Search fields, scope, and intended workflow are each stated efficiently.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema and safety annotations, so the description need not explain return values or read-only behavior. It covers the core search behavior and airport scope, though the limit parameter remains undocumented in prose.

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 description coverage is 0%, so the description should compensate. It explains the required q parameter well by listing searchable fields, but it does not mention the limit parameter or its constraints.

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 states a specific verb and resource: search airports by name, city, IATA or ICAO code. It also scopes the result set to large and medium airports, which distinguishes it from broader airport tools.

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?

It gives clear usage context: use this to find an airport's ICAO code before calling other airport tools. It does not explicitly name alternatives or when not to use it, but the intended workflow is clear.

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

All FlightDB 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.