Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_get_flight_track

Read-only

Retrieve a flight's position track (breadcrumb log) by fa_flight_id to visualize the route flown and fill gaps with estimated positions when actual data is missing.

Instructions

Get the position track (breadcrumb log) for a specific flight by fa_flight_id.

Input Schema

NameRequiredDescriptionDefault
idYesfa_flight_id of the flight
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.
include_estimated_positionsNoInclude estimated positions where actual data is missing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.2
    • changedInput schema / properties / id / pattern
      Previous value: -"^[A-Za-z0-9.-]+$"New value: +"^[A-Za-z0-9][A-Za-z0-9.-]*$"
  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. 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 semantic that the response is a track/log rather than a snapshot, but says nothing about the time span covered, sampling density, or pagination of the breadcrumb points.

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 front-loaded sentence with no filler; the resource and the identifying parameter are both stated immediately.

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 read-only tool with full schema coverage and no output schema, the definition is minimally adequate but leaves the most important contextual gap unaddressed: how this track differs from fa_get_flight_position and fa_get_flight_history in the same family. An agent picking among these five siblings gets no help.

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%, so all three parameters (id, view, include_estimated_positions) are already fully documented in the schema, including the enum values and the compact/full tradeoff. The description adds no parameter meaning beyond restating that the id is an fa_flight_id, 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?

The description gives a specific verb and resource ('Get the position track (breadcrumb log) for a specific flight'), and 'breadcrumb log' usefully characterizes the resource as a series of positions rather than a single point. However, it never distinguishes itself from near-identical siblings like fa_get_flight_position, fa_get_flight_history, or fa_get_flight_route.

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?

There is no when-to-use guidance at all, which is a real problem given five sibling tools (fa_get_flight_position, fa_get_flight_route, fa_get_flight_map, fa_get_flight_history, fa_search_flight_positions) that an agent could easily confuse with this one. Nothing states when the breadcrumb track is the right call versus a single position or a history.

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