Skip to main content
Glama

US airport delays and ground stops

airport_delays
Read-only

Check US airport delays from the FAA's live National Airspace System status: ground stops, ground delay programs, arrival and departure delays (with minutes, trend and reason) and closures. Give an airport code, or none to list every airport with delays right now.

$0.003 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote.

When to use: You need to know if a US airport has delays or a ground stop right now. Parameters: airport: a US code like JFK or KJFK; leave out to list every airport with delays. Returns: ground stops, ground delay programs, arrival and departure delays (minutes, trend, reason) and closures, live from the FAA.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "airport_delays"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportNoUS airport code, e.g. "JFK" or "KJFK". Leave out to list every airport with delays.
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly and openWorld annotations, the description discloses the live FAA data source, the exact delay categories returned, the x402 pricing model, that failed calls cost nothing, and the quote-then-pay workflow. This is substantial behavioral context that an agent needs before invoking a paid live-data tool.

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 front-loaded with purpose, then usage, parameters, and returns, with no wasted preamble. It repeats the returned delay categories in both the opening sentence and the Returns section, which is slightly redundant but not harmful.

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?

There is no output schema, but the description explains the return categories clearly. It also covers the payment workflow, live data source, and cost model, so an agent has enough information to call the tool correctly.

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 both parameters are already documented in the input schema. The description reinforces the airport code behavior and payment quote flow, but it does not add syntax or format details beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb and resource: checking US airport delays from the FAA's live National Airspace System status. It enumerates the exact data covered, including ground stops, ground delay programs, arrival/departure delays, and closures, so an agent can distinguish this from unrelated sibling tools.

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?

It gives an explicit when-to-use condition: when the agent needs to know if a US airport has delays or a ground stop right now. It also explains the no-airport behavior, but it does not name alternatives or when-not-to-use cases, which keeps it below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.