Skip to main content
Glama
Sign In
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_get_nearby_airports

Read-only

Locate airports within a given statute-mile radius of a latitude and longitude, optionally filtering to fields with a published instrument approach.

Instructions

Find airports near a latitude/longitude within a radius (statute miles).

Input Schema

NameRequiredDescriptionDefault
viewNoResponse shape: "compact" (default) drops fields the response already carries elsewhere; "full" returns every field this server understands. compact strips image/avatar URLs from the response; "full" returns FlightAware's payload untouched. No field projection: this server has no verified record of which FlightAware fields matter, and inventing one would risk dropping a field a caller needs.
cursorNoPaging cursor: the cursor query parameter of a previous response's links.next (passing the whole links.next value also works)
radiusYesSearch radius in statute miles
latitudeYesLatitude in decimal degrees
only_iapNoOnly airports with a published instrument approach
longitudeYesLongitude in decimal degrees
max_pagesNoMax pages to fetch, 1-20 (AeroAPI default: 1). Capped at 20 since AeroAPI bills per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.2
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque paging cursor from a previous response's links.next"New value: +"Paging cursor: the cursor query parameter of a previous response's links.next (passing the whole links.next value also works)"
  2. Changed1 schema field changedv1.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changedv0.5.2
    • addedInput schema / properties / view
      Added value: +{
+  "description": "Response shape: \"compact\" (default) drops fields the response already carries elsewhere; \"full\" returns every field this server understands. compact strips image/avatar URLs from the response; \"full\" returns FlightAware's payload untouched. No field projection: this server has no verified record of which FlightAware fields matter, and inventing one would risk dropping a field a caller needs.",
+  "enum": [
+    "compact",
+    "full"
+  ],
+  "type": "string"
+}
  4. Changed2 schema fields changedv0.3.2
    • changedInput schema / properties / max_pages / description
      Previous value: -"Max pages to fetch (AeroAPI default: 1)"New value: +"Max pages to fetch, 1-20 (AeroAPI default: 1). Capped at 20 since AeroAPI bills per page."
    • changedInput schema / properties / max_pages / maximum
      Previous value: -9007199254740991New value: +20
  5. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the unit of measure (statute miles) for the radius, which is genuinely useful, but says nothing about pagination behavior, per-page billing, or response shape. With annotations doing the heavy lifting, this is a modest but real contribution.

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?

A single tight sentence with the primary constraint (lat/lon proximity) front-loaded and zero filler. Nothing to trim.

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

Completeness3/5

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

For a 7-parameter geo-search tool with no output schema, the schema documentation is thorough, so the description does not need to explain return values. It is nevertheless thin on routing (when this beats fa_list_airports) and silent on paging and billing, which the least-surprising invocation would want.

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 100% and every parameter (view, cursor, only_iap, max_pages, radius, latitude, longitude) is documented in the schema itself. The description restates only the radius units, adding nothing beyond the structured fields, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear specific verb 'Find' with resource 'airports' and the qualifying constraints (latitude/longitude, radius). An agent can tell this is a geospatial proximity search. However, it does not distinguish itself from sibling list/search tools such as fa_list_airports or fa_get_airport, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no prerequisites, and no mention of alternative tools. The agent must infer that this is the right tool when it has coordinates rather than an airport code; sibling routing to fa_list_airports or fa_resolve_airport is absent.

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

Deploy Server

Other Tools