Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_get_scheduled_flights

Read-only

Retrieve airline-scheduled flights between two dates, with optional filters for origin, destination, airline, or flight number.

Instructions

Get airline-scheduled flights between two dates (YYYY-MM-DD), optionally filtered by origin, destination, airline, or flight number.

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)
originNoFilter by origin airport code
airlineNoFilter by operator (airline) code
date_endYesEnd date, YYYY-MM-DD
max_pagesNoMax pages to fetch, 1-20 (AeroAPI default: 1). Capped at 20 since AeroAPI bills per page.
date_startYesStart date, YYYY-MM-DD
destinationNoFilter by destination airport code
flight_numberNoFilter by flight number
include_codesharesNoInclude codeshare duplicates

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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, covering the safety profile. The description adds only the implicit scheduled-vs-actual distinction and the date-range requirement; it says nothing about pagination behavior, per-page billing, or rate limits, all of which the schema carries instead.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One well-formed sentence with the resource up front and the filter list trailing, so the key information lands first. The filter enumeration adds little that the schema doesn't already give, but the sentence is short enough that the redundancy costs almost nothing.

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 10-parameter, paginated, per-page-billed endpoint, the description omits any mention of paging, cost, or result scope, relying on the schema for all of it. With full schema coverage and an annotated safety profile that is minimally acceptable, but the description does not carry its share for a tool of this complexity.

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 every parameter (view, cursor, max_pages, include_codeshares, codes, dates) is already documented in the schema, often richly. The description's filter list merely restates four of the ten parameters and adds no format or semantic detail beyond the schema.

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?

States a specific verb ('Get') and resource ('airline-scheduled flights') with a clear range constraint, so the purpose is unambiguous. However, it does nothing to distinguish itself from close siblings like fa_get_flights, fa_search_flights, or fa_search_flights_advanced, which an agent must disambiguate by name alone.

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?

The description never says when to choose this tool over the many overlapping flight-lookup siblings, nor does it state any exclusions or prerequisites. The 'optionally filtered by' clause lists capabilities rather than usage conditions, leaving routing entirely to inference.

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