Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_search_flights_advanced

Read-only

Search flights using structured predicates on fields like airline, destination, altitude, and status. Build precise queries with operators (match, >, =) to filter live flight data.

Instructions

Search flights using AeroAPI's full structured query language (more expressive than fa_search_flights). The query is a space-separated list of {operator key value} predicates, e.g. "{match ident UAL*} {> alt 300} {= dest KLAX}". Operators: true/false/null/notnull/=/!=/</>/<=/>=, match/notmatch (case-insensitive wildcards), range (two values), in/orig_or_dest/aircraftType/ident/ident_or_reg ({a b c} value lists), airline (1=airline, 0=GA). Common keys: ident, orig, dest (ICAO codes), aircraftType, alt (hundreds of ft), prefix, lifeguard, cancelled, arrived.

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 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. Changed1 schema field changedv0.2.0
    • changedInput schema / properties / query / description
      Previous value: -"Boolean query expression"New value: +"Structured \"{operator key value}\" query, e.g. {match ident UAL*} {> alt 300}"
  5. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds meaningful behavioral context by explaining how the query is parsed as space-separated predicates, listing the supported operators, and giving example syntax—this goes well beyond the structured 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?

Dense but efficient: it front-loads the purpose, then packs the query syntax, operators, example, and common keys into a compact set of clauses. Every part earns its place given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only search tool with four parameters, the description plus rich schema provides everything needed: the query predicate language, operators, keys, example, and schema explanations for view/cursor/max_pages. No obvious required usage detail is missing.

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 schema already documents all parameters. The description adds real value beyond that by explaining the query format, operator semantics, common keys, and ICAO code conventions, which the schema only sketches.

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?

States a specific verb and resource ("Search flights") and immediately distinguishes itself from the sibling fa_search_flights by calling it more expressive. The query-language detail makes it unmistakable what this tool does.

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 description implies when to use this tool by comparing it to fa_search_flights (more expressive), giving a clear reason to choose it over the simpler sibling. It does not explicitly state when-not-to-use it or name other alternatives, but the contrast 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