Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_get_flights

Read-only

Retrieve recent, current, and scheduled flights for a flight designator, aircraft registration, or FlightAware flight ID.

Instructions

Get flights for an ident — a flight designator (e.g. UAL123, AAL100), aircraft registration (e.g. N12345), or fa_flight_id. Returns recent, current, and scheduled flights for that ident.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNoISO-8601 end of the time window
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.
identYesFlight designator, registration, or fa_flight_id
startNoISO-8601 start of the time window
cursorNoOpaque paging cursor from a previous response's links.next
max_pagesNoMax pages to fetch, 1-20 (AeroAPI default: 1). Capped at 20 since AeroAPI bills per page.
ident_typeNoDisambiguate how `ident` is interpreted

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. 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
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true, so the agent knows this is a safe read operation. The description adds that it returns 'recent, current, and scheduled flights' for the ident, which is useful behavioral context. The view parameter description is notably transparent about the compact/full distinction and explicitly admits the server has no verified record of which fields matter, which is honest and helpful. However, it doesn't mention pagination behavior beyond the cursor/max_pages parameters, which are already in the schema.

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 zero waste. The first sentence states the core purpose and defines the key term (ident). The second sentence states the return scope. The view parameter description is longer but earns its place by explaining a non-obvious trade-off and admitting a limitation. Everything is front-loaded.

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?

For a read-only lookup tool with 100% schema coverage and no output schema, the description is quite complete. It defines the input (ident), the scope (recent/current/scheduled), and the view trade-off. The main gap is that it doesn't describe the return format or what fields the response contains, but with no output schema and the view parameter explicitly saying the server doesn't track which fields matter, this is a reasonable limitation. The openWorldHint annotation also signals that the response may contain unexpected fields.

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 description coverage is 100%, so the schema already documents all 7 parameters. The description adds value by explaining what an 'ident' is (designator, registration, or fa_flight_id) and that the tool returns recent/current/scheduled flights. The view parameter description is exceptionally detailed, explaining the exact trade-off between compact and full. The description doesn't add much beyond the schema for start/end/cursor/max_pages, but the schema already covers those well.

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 ('Get flights') and resource ('for an ident'), and explicitly defines what an ident can be (designator, registration, or fa_flight_id). It distinguishes itself from sibling search tools by focusing on a single ident rather than a search query, and the ident_type parameter further disambiguates interpretation.

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 clearly states when to use this tool: when you have an ident (designator, registration, or fa_flight_id) and want recent, current, and scheduled flights for it. It doesn't explicitly name alternatives like fa_search_flights for when you don't have an ident, but the ident-centric framing makes the usage context clear. The ident_type parameter also provides guidance on how to disambiguate the ident.

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