faa-traffic-delays-mcp-server

List ATCSCC Advisories

faa_delays_list_advisories

Read-onlyIdempotent

List the ATCSCC advisories issued on one UTC date, newest first, from the FAA advisories database's per-date index: ground stops and delay programs as issued, proposed, revised, and canceled, required reroutes, flow constrained areas, operations plans, and CDM compression advisories, including those no longer active and those on past dates, which the NAS Status feed does not carry. Each row gives the advisory number, control element, subject, any further title lines (a reroute's name, constrained area, and valid period), and send time; its number and date open the full text with faa_delays_get_advisory. Narrow by categories, control_element (an airport, its ICAO code, an ARTCC, or DCC for national advisories), or query (literal case-insensitive subject/details text, such as an FCA name); filters combine before limit and offset paging.

Input Schema

Name	Required	Description
`date`	No	UTC date to list, YYYY-MM-DD; MM/DD/YYYY and M/D/YYYY are also accepted. Omit for today (UTC). No later than tomorrow (UTC); past dates remain available.
`limit`	No	Advisories per page, 1–200.
`query`	No	Literal case-insensitive substring of subject or any details line, such as FCA005; combined with categories and control_element before paging. Omit to match every title.
`offset`	No	Matching advisories to skip, for paging: nextOffset from the previous page.
`categories`	No	Only advisories the FAA files under these categories: ground_stop, ground_delay_program, airspace_flow_program, ctop, route, other (flow constrained areas and operations plans file under other). Also accepts gs, gdp, afp, spelled-out names such as "ground stop", and a comma-separated string; case-insensitive. Omit for every advisory, including CDM compression advisories, which the FAA files under no category.
`control_element`	No	Only advisories whose control element is this facility or lists it as a part: an airport by FAA identifier (ORD) or ICAO code (KORD), an ARTCC (ZAU), a pair (ORD/ZAU or KORD/ZAU), or DCC for national advisories such as reroutes and the operations plan. Case-insensitive. Airports named only in a subject or details do not match.

Output Schema

Name	Required	Description
`cap`	No	The limit applied; present only when more advisories remain.
`date`	No	The UTC date read, YYYY-MM-DD; today (UTC) when date was omitted.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Advisories on this page; present only when more remain.
`notice`	No	Guidance on an empty date, a filter that matched nothing, an offset past the end, more pages, and index rows that could not be read.
`truncated`	No	True when matching advisories remain past this page; absent otherwise.
`advisories`	No	Advisories issued on date that match categories, control_element, and query, newest first: up to limit of them, starting at offset.
`nextOffset`	No	offset of the next page; present while matching advisories remain past this one.
`totalCount`	No	Advisories on date that match categories, control_element, and query, before paging.
`appliedQuery`	No	Trimmed text query matched against subjects and details; absent when unset.
`appliedCategories`	No	The categories filter as the server normalized it; absent when omitted, which reads every advisory, uncategorized ones included.
`appliedControlElement`	No	The control_element filter as the server matched it: uppercased, each ICAO airport code in it mapped to its FAA identifier (KORD → ORD, KORD/ZAU → ORD/ZAU); absent when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 14, 2026

addedInput schema / properties / query

Added value: +{
+  "description": "Literal case-insensitive substring of subject or any details line, such as FCA005; combined with categories and control_element before paging. Omit to match every title.",
+  "type": "string"
+}

changedOutput schema / properties / advisories / description

Previous value: -"Advisories issued on date that match categories and control_element, newest first: up to limit of them, starting at offset."New value: +"Advisories issued on date that match categories, control_element, and query, newest first: up to limit of them, starting at offset."

addedOutput schema / properties / appliedQuery

Added value: +{
+  "description": "Trimmed text query matched against subjects and details; absent when unset.",
+  "type": "string"
+}

changedOutput schema / properties / totalCount / description

Previous value: -"Advisories on date that match categories and control_element, before paging."New value: +"Advisories on date that match categories, control_element, and query, before paging."

First observedOct 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety profile is covered. The description adds genuine behavioral context: newest-first ordering, inclusion of inactive/past advisories, and the exact row contents (advisory number, control element, subject, title lines, send time). It omits rate limits or pagination edge behavior, but the added context is meaningful.

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?

Front-loads the core action and scope in the first clause, and every sentence carries information. However, it is a very dense, comma-heavy run-on that could be split for easier scanning, slightly reducing readability.

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 filtered, paginated list tool with a 100%-covered schema, output schema, and full annotations, nothing essential is missing. The description even explains row fields and the cross-reference to the full-text tool, exceeding what the structured fields require.

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 the schema already documents every parameter in depth, including enum synonyms and the DCC/ICAO forms. The description largely restates these; its only real addition is that filters combine before limit/offset paging. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (List) and resource (ATCSCC advisories) with explicit scope: advisories issued on one UTC date, newest first, from the per-date index. The enumeration of advisory kinds (ground stops, reroutes, flow constrained areas, operations plans, CDM compression) and the 'NAS Status feed does not carry' clause let an agent distinguish it from siblings without opening the schema.

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?

Gives clear context for use — it covers historic/inactive advisories and per-date index entries the NAS Status feed lacks — and routes the agent to the sibling faa_delays_get_advisory to open full text. It does not explicitly state when not to use it versus list_active_events or get_operations_plan, so it stops short of full when/when-not coverage.

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.