airport-delays-faa-status-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
US airport delays read at call time from the FAA National Airspace System status (nasstatus.faa.gov): ground stops, ground delay programs, arrival and departure delays, closures and deicing. A model cannot know whether an airport has a ground stop right now. Use airport_delays_now for "airport delays today", airport_status for one airport ("is there a ground stop at JFK", "delays at O'Hare") and airport_delays_check_trip for an itinerary. These are FAA traffic programs; a single flight's delay or cancellation comes from the airline and is not here.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| airport_delays_nowA | All US airports with an active FAA event right now: ground stops, ground delay programs (average and maximum delay, reason such as weather or volume, end time), general arrival and departure delays with trend, airport closures and deicing, sorted worst first, plus airspace flow programs. |
| airport_statusA | FAA delay status of one US airport, by IATA code (JFK), ICAO code (KJFK), airport name or city (Newark, O'Hare, Denver): any ground stop, ground delay program, arrival or departure delay, closure or deicing with reason, minutes and end time, or a clear statement that the FAA reports no delay there; plus the runway configuration and arrival rate when posted. |
| airport_delays_check_tripA | Check every airport on an itinerary (origin, connections, destination; 1 to 8 airports) for FAA ground stops, ground delay programs, delays and closures in one call. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three tools have clearly distinct scopes: a nationwide snapshot, a single-airport lookup, and an itinerary check. Although airport_delays_now and airport_delays_check_trip both cover multiple airports, their purposes and inputs are explicit enough to avoid misselection.
All names use snake_case and are readable, but the prefix pattern is slightly mixed: two use airport_delays_* while one uses airport_status. The structure airport_delays_check_trip also blends noun and verb phrasing more than the others.
Three tools is well-scoped for a focused FAA airport-delay status server. Each tool covers a distinct access pattern—global, single-airport, and itinerary—with no redundant or filler tools.
The surface covers the core current-status workflows: all active events, one airport, and multi-airport itineraries. Minor gaps exist, such as filtering by region or delay type, but agents can work around them using the existing tools.