Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_search_flight_positions

Read-only

Find live aircraft positions using structured {operator key value} queries, such as {match ident UAL*} or {> alt 300}, to get real-time location points instead of flight summaries.

Instructions

Search live flight POSITIONS using the structured "{operator key value}" query language (same grammar as fa_search_flights_advanced — NOT the simplified "-key value" syntax). Returns position points rather than flight summaries. Example: {match ident UAL*} {> alt 300}.

Input Schema

TableJSON 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.
queryYesStructured "{operator key value}" query, e.g. {match ident UAL*} {> alt 300}
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.

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. Addedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

While annotations already declare readOnlyHint=true and openWorldHint=true, the description adds behavioral context beyond the annotations: it states results are 'live' (implying temporal sensitivity) and describes the output nature ('returns position points rather than flight summaries'). This provides useful response-shape expectations without repeating structured attributes and does not contradict the annotations.

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?

Three sentences: one states purpose and grammar, one clarifies the output type, and one gives a concrete example. Every sentence earns its place, no filler, and the key differentiator ('NOT the simplified '-keys' syntax') is strategically placed early.

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 four-parameter tool with no output schema, the description is nearly self-sufficient: it covers the query format, clarifies the difference from the advanced search tool, and describes the return semantics (position points). The schema already handles view/cursor/max_pages, and the description does not need to repeat those. It would be slightly improved by a note on output structure (e.g., list of point objects), but the missing piece is minor given annotations supply safety and currency signals.

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% so the baseline is 3, but the description adds real value by clarifying the query parameter's grammar and explicitly disassociating this tool from the simplified syntax, which is not in the schema. The example '{operator key values}' is repeated but the new 'NOT the simplified' cross-referencing helps the agent avoid a common mistake without opening any other definition.

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 clearly identifies the resource as 'live flight POSITIONS' with the specific verb 'Search', and immediately differentiates from the sibling tool by name: it returns 'position points rather than flight summaries'. This makes the tool's function and distinguishing purpose unmistakable, even without opening the schema.

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 explicitly tells the model to use the structured '{operator key value}' query language and warns against the simplified '-key value' syntax, giving a concrete, actionable guidance for correct use. It references the sibling tool fa_search_flights_advanced by name and implies a choice based on output type (positions vs. summaries), though it stops short of an explicit conditional like 'when you need positions, use this; when you need summaries, use X'.

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