faa-traffic-delays-mcp-server

List FAA Delay Reference Data

faa_delays_list_reference

Read-onlyIdempotent

Decode the vocabulary the other faa_delays tools return: event types and their fields, traffic-management terms (AAR, EDCT, FCA, GDP, SWAP), ARTCC center codes, the FAA pacing airports with time zones, and accepted identifier formats.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	Yes	What to decode: event_types (event types and their key fields), terms (traffic-management abbreviations), artccs (ARTCC center codes and names), pacing_airports (the FAA pacing airports with time zones, read live), or identifiers (accepted airport-code, advisory, and time formats). Case-insensitive; spaces and hyphens read as underscores.

Output Schema

TableJSON Schema

Name	Required	Description
`error`	No	Present when the call failed. Absent on success.
`terms`	No	Present for topic terms, alphabetical.
`topic`	No	The topic this result decodes.
`artccs`	No	Present for topic artccs, by code: the 25 US ARTCCs, including the New York and Oakland oceanic centers, plus Anchorage Oceanic, Guam, Auckland Oceanic, Toronto, and Vancouver, the other facilities NASR names as an airport's ARTCC. Every artcc faa_delays_get_airport_status returns is listed.
`notice`	No	Unreadable pacing-airport rows omitted from this snapshot.
`fetchedAt`	No	Present for topic pacing_airports: when this server fetched the list from the FAA (UTC ISO).
`eventTypes`	No	Present for topic event_types, in severity order.
`identifiers`	No	Present for topic identifiers.
`pacingAirports`	No	Present for topic pacing_airports: the FAA pacing airports, read live and cached 6 h.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 14, 2026

addedOutput schema / properties / notice

Added value: +{
+  "description": "Unreadable pacing-airport rows omitted from this snapshot.",
+  "type": "string"
+}

addedOutput schema / properties / pacingAirports / items / properties / reportedTimezone

Added value: +{
+  "description": "Original FAA time zone when a verified correction was applied.",
+  "type": "string"
+}

changedOutput schema / properties / pacingAirports / items / properties / timezone / description

Previous value: -"IANA-style time zone the FAA assigns (US/Pacific); FAA-supplied text."New value: +"Effective IANA time zone; PHX reported as US/Mountain is corrected to America/Phoenix."

First observedOct 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safe/idempotent profile is covered. The description adds that pacing_airports data is 'read live', hinting at freshness behavior, but that detail is largely duplicated in the schema and no other behavioral traits (caching, response size, rate limits) are disclosed.

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?

A single front-loaded sentence that leads with the high-value framing ('decode the vocabulary the other faa_delays tools return'). It is tightly written, though the enumerated topic list partially duplicates the schema's enum, making it slightly longer than strictly necessary.

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?

An output schema exists, so return values need not be explained, and the enum fully specifies the input. For a single-enum reference-lookup tool the description is nearly complete; only minor behavioral detail (freshness/scope of the 'read live' data) is left implicit.

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% and the single `topic` enum is documented in full detail with per-value meanings. The description's topic list mirrors the enum without adding syntax or format guidance beyond it, so the schema does the heavy lifting and 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?

States a specific verb ('Decode the vocabulary') and names the exact resource: reference data for event types, terms, ARTCC codes, pacing airports, and identifier formats. It explicitly distinguishes itself from the sibling tools by describing itself as the decoder for what 'the other faa_delays tools return'.

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 framing 'decode the vocabulary the other faa_delays tools return' clearly signals when an agent should reach for this tool: when it needs to interpret opaque codes from the sibling tools. It stops short of stating exclusions or naming a specific alternative, so it is clear context rather than explicit routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All faa-traffic-delays-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.