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

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.
cursorNoOpaque paging cursor from a previous response's links.next
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 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

A3.6/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, covering the read and open-world behavior. The description adds the 'airline-scheduled' scope and filter capabilities, but does not disclose further behavioral traits such as pagination or codeshare handling; those live in the schema. There is no contradiction with 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?

One sentence, front-loaded with the required date range and followed by the optional filters. There is no wasted wording, and the structure matches the tool's invocation pattern.

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 10-parameter tool, the schema richly covers required dates, filter patterns, pagination, and response view options, so the description does not need to repeat those. The only notable gap is the lack of guidance for selecting this tool over sibling flight-search tools, but the core invocation context is complete.

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 already has meaningful documentation. The description adds marginal value by summarizing the main filters, but it does not provide any information beyond what the schema already contains.

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 states a specific verb ('Get'), a specific resource ('airline-scheduled flights'), and the required date-range scope plus optional filters. It does not explicitly distinguish this from sibling flight-lookup tools, but the 'airline-scheduled' qualifier makes the resource clear enough for an agent to identify its core purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage: scheduled flight lookups over a date range, optionally narrowed by origin, destination, airline, or flight number. However, it gives no explicit when-to-use versus alternatives such as fa_get_flights, fa_search_flights, or fa_get_operator_flights, and it names no exclusions.

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