Skip to main content
Glama
chrischall

flightaware-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fa_get_airport_weather

Read-only

Retrieve current METAR observations or TAF forecast for any airport using its ICAO, IATA, or LID code. Choose between compact or full response views.

Instructions

Get weather for an airport: current METAR observations, or the TAF forecast.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAirport code (ICAO/IATA/LID)
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
reportNoobservations (METAR) or forecast (TAF)observations
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. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations indicate readOnly (safe) and openWorld (external data). The description adds context by mentioning report types but doesn't elaborate on external dependencies or rate limits. However, the parameter descriptions for 'view' and 'max_pages' disclose important behavior (admitting uncertainty about field projection, billing per page), which is notable and transparent.

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?

The description is concise with two clear clauses. It front-loads the primary purpose ('Get weather for an airport') and specifies the key options. It is appropriately sized, though slightly under-detailed on usage scenarios.

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 5-parameter tool with no output schema, the description is fairly complete. It covers the core functionality and hints at response shapes (via 'view'), but lacks explicit mention of pagination (cursor) in the description, though schema covers it. Given the complexity, a brief note on pagination would improve completeness.

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%, with each parameter described in the schema (e.g., 'id' as airport code, 'report' with enum, 'view' with detailed explanation). The description itself adds minimal extra meaning, so the baseline of 3 is appropriate per the criteria.

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 states the tool's verb ('Get') and resource ('airport weather') and specifies the two report types (METAR observations and TAF forecast). It distinguishes from sibling tools like fa_get_airport (airport info) and fa_get_airport_delays (delays), making its purpose unambiguous.

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 usage for weather data via the 'report' parameter, but does not explicitly contrast with alternatives like fa_get_airport for non-weather info. A clear statement like 'Use this for weather only; use fa_get_airport for general airport details' would be stronger, but the purpose is evident enough.

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