Skip to main content
Glama

FAA airport delays (x402)

FAA airport delays right now, in one call: current delays and closures with ground delay programs, ground stops, arrival

airport_delays
Read-onlyIdempotent

FAA airport delays right now, in one call: current delays and closures with ground delay programs, ground stops, arrival/departure delays and closures by airport with reason and duration (airport=3-letter code optional). Pay per call $0.002 USDC on Base via x402.

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
airportNo3-letter code, e.g. SFO
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds genuinely useful behavior beyond that: it is a paid call ($0.002 USDC on Base via x402), and the schema explains the first-call payment handshake, though there is no mention of response shape or data freshness limits.

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-loaded and only two sentences, with the payment caveat placed at the end where it belongs. It does repeat itself slightly ('current delays and closures' appears twice) and largely mirrors the title, which is minor waste.

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 two-parameter, optional-input, no-output-schema tool, the description covers what data comes back (delays, closures, ground stops, reasons, durations) and the payment mechanics. What is missing is any statement of geographic coverage or how current the snapshot is.

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 the airport format ('3-letter code, e.g. SFO') and the x_payment handshake both documented in the schema itself. The description repeats the 'airport=3-letter code optional' hint but adds no meaning beyond the structured fields, so the baseline of 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?

Names a specific resource and scope: FAA airport delays right now, including ground delay programs, ground stops, arrival/departure delays, reasons and durations. It is clearly distinct from the weather siblings, which cover forecasts and alerts rather than FAA operational status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'right now' framing and the optional airport argument imply real-time lookup, either system-wide or per airport, but the description never states when to prefer this tool over weather_alerts or weather_forecast, nor any exclusion or precondition.

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.

Resources