Skip to main content
Glama

airports

by io.github.pipeworx-io

Search Airports

search_airports
Read-onlyIdempotent

Look up an airport by city name (e.g. "Tokyo", "New York", "London") OR by 3-letter IATA code (e.g. "JFK", "LHR"). City lookup uses a bundled map of the top ~150 international hubs; cities with multiple airports return all primary ones. For airports not in the bundle, pass an IATA code or use the aviationstack pack for full-text name/country search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesCity name (e.g. "Chicago", "London") or 3-letter IATA code (e.g. "ORD")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageYesCurrent page number
countYesNumber of results returned
resultsYesList of airports matching the search query

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedInput schema / examples
      Previous value: -[
-  {
-    "query": "New York"
-  },
-  {
-    "page": 2,
-    "query": "London"
-  }
-]New value: +[
+  {
+    "query": "New York"
+  },
+  {
+    "query": "London"
+  }
+]
  2. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"3-letter IATA airport code (e.g. \"DEN\" for Denver International)"New value: +"City name (e.g. \"Chicago\", \"London\") or 3-letter IATA code (e.g. \"ORD\")"
  3. Changed2 schema fields changed
    • removedInput schema / properties / page
      Removed value: -{
-  "description": "Page number for pagination (default: 1)",
-  "type": "number"
-}
    • changedInput schema / properties / query / description
      Previous value: -"Airport name, city, or country to search for"New value: +"3-letter IATA airport code (e.g. \"DEN\" for Denver International)"
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of results returned",
+      "type": "number"
+    },
+    "page": {
+      "description": "Current page number",
+      "type": "number"
+    },
+    "results": {
+      "description": "List of airports matching the search query",
+      "items": {
+        "properties": {
+          "altitude_ft": {
+            "description": "Altitude in feet",
+            "type": "number"
+          },
+          "city": {
+            "description": "City where airport is located",
+            "type": "string"
+          },
+          "country": {
+            "description": "Country where airport is located",
+            "type": "string"
+          },
+          "iata": {
+            "description": "Three-letter IATA code",
+            "type": "string"
+          },
+          "icao": {
+            "description": "Four-letter ICAO code",
+            "type": "string"
+          },
+          "latitude": {
+            "description": "Latitude coordinate",
+            "type": "number"
+          },
+          "longitude": {
+            "description": "Longitude coordinate",
+            "type": "number"
+          },
+          "name": {
+            "description": "Airport name",
+            "type": "string"
+          },
+          "timezone": {
+            "description": "Airport timezone",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "results",
+    "count",
+    "page"
+  ],
+  "type": "object"
+}
  5. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "New York"
+  },
+  {
+    "page": 2,
+    "query": "London"
+  }
+]
  6. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations: the bundled map of 150 hubs, the behavior of returning all primary airports for multi-airport cities, and the limitation that city lookup only works for bundled airports.

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 two sentences, with the first stating input types and the second explaining scope and limitation. All sentences earn their place, with no fluff or redundancy, and the key information is front-loaded.

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 and annotations cover safety, the description is complete: it explains input types, behavior, scope, limitations, and an alternative for non-bundled airports. The tool is simple (1 param) and the description fully covers usage context.

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% (query described as city or IATA code with examples), so baseline is 3. The description adds meaning by explaining that city lookup relies on a bundled map of 150 top hubs and that multi-airport cities return all primary ones, which is not in the schema.

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 uses a specific verb ('look up') and resource ('airport'), and clearly distinguishes the tool's scope by specifying input modes (city name or IATA code) and the bundled map limitation. This separates it from sibling tools like get_airport or more comprehensive search alternatives by explicitly noting the top-150-hub limitation.

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?

It explicitly states when to use the tool: for city name or IATA code lookups within the bundled map of 150 hubs. It also provides when-not guidance: for airports not in the bundle, pass an IATA code or use the aviationstack pack for full-text name/country search, naming an alternative.

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

All airports toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0
Disambiguation2/5

Many tools have distinct purposes, but the three 'ask_pipeworx' variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded) are highly similar and likely cause confusion. Additionally, the toolset mixes airport-specific tools with unrelated financial and research tools, creating ambiguity about when to use which.

Naming Consistency2/5

Naming conventions are inconsistent: some tools use descriptive snake_case (ai_visibility_check, ask_pipeworx), others are single verbs (remember, forget, recall), and some include brand names (pipeworx_feedback). No clear pattern emerges across the 34 tools.

Tool Count1/5

34 tools is excessive for a server named 'airports'—only 3 tools directly relate to airports (search_airports, get_airport, calculate_distance). The majority are unrelated utilities (financial, prediction markets, memory), making the scope far too broad and unfocused.

Completeness1/5

The server severely lacks completeness for its stated airport domain: there are no tools for flights, airlines, runways, or real-time data. The other included domains (e.g., financial, prediction markets) are also incomplete, with e.g., only partial coverage of company data and no update/delete operations.

Resources