Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Current FAA airport delays and closures in one call: ground delay programs, ground stops, arrival/departure delays and c

airport_delays
Read-onlyIdempotent

Current FAA airport delays and closures in one call: 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.7/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 the baseline is covered. The description adds essential behavior they do not: the call is paid ($0.002 USDC on Base via x402), and it is live/current data rather than historical. Rate limits and error/failure behavior are still unstated.

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?

Two sentences, front-loaded with what the agent gets, followed by the pricing/payment constraint. Nearly every clause carries information, though the enumeration of delay types overlaps heavily with the title.

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?

With no output schema, the description does the work of describing return content (delays and closures with reason and duration, grouped by airport), and it explains the payment flow sufficiently for an agent to attempt a call. It omits response shape and coverage scope (e.g., which airports or regions), which is a modest gap.

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%, including a full explanation of the x402 payment handshake, so the schema already carries both parameters. The description's parenthetical 'airport=3-letter code optional' merely restates what the schema declares, adding no new semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (current FAA airport delays and closures) and enumerates the exact record types returned: ground delay programs, ground stops, arrival/departure delays, with reason and duration. It does not differentiate itself from a plausible alternative like weather_alerts, so it falls short of a 5.

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?

Usage is implied rather than stated: an agent can infer this is for checking live airport conditions, and the optional airport code implies both a nationwide and per-airport query mode. There is no explicit when-not guidance or pointer to any related tool.

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