Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_get_operator_flights

Read-only

Retrieve an airline's flight board with options for all, arrivals, departures, enroute, or scheduled flights. Use it to get current or planned flights for any operator.

Instructions

Get a flight board for an operator (airline): all flights, or arrivals/departures/enroute/scheduled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesOperator code (ICAO/IATA)
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.
boardNoWhich board to fetch (default: all)all
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 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"
  2. 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"
+}
  3. 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
  4. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true, and the description's 'Get' is consistent with that. The description does not add behavioral detail like pagination behavior, rate limits, or response-size caveats, but those are not necessary to correct for the read-only annotation. It adds board enumeration as domain scope rather than novel behavioral disclosure.

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?

One sentence, front-loaded with the key scoping concept ('operator'), and every word earns its place. It avoids repeating schema details while still conveying the tool's purpose.

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?

The one-line description plus a rich 100%-coverage schema suffices for correct selection and invocation: the required id, board enum, view behavior, and pagination are all documented. There is no output schema, so a brief note about return shape could have helped, but the tool is a straightforward read-only board query and nothing critical is missing.

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 coverage is 100%, so the structured definitions already document every parameter. The description's 'arrivals/departures/enroute/scheduled' merely echoes the board enum, and 'operator (airline)' restates what the id schema already says. The description adds no meaningful semantic value beyond the schema, so the baseline 3 applies.

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?

Description names a specific verb ('Get'), a resource ('flight board for an operator/airline'), and the board variants ('arrivals/departures/enroute/scheduled'). This clearly distinguishes it from sibling tools that cover flights, airports, tracks, or aircraft by making the operator scoping explicit.

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 phrase 'for an operator (airline)' gives clear selection context, separating this tool from fa_get_airport_flights and fa_get_flights. It does not explicitly name alternatives or exclusion conditions, so it falls short of a 5, but the intended use case is clear.

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