Skip to main content
Glama

Airport delays (10 sats L402 or $0.01 USDC x402)

get_airport_delays
Read-only

US airport ground stops, delay programs, arrival/departure delays and closures from the FAA NAS Status snapshot (optional airport=SFO). Not for navigation. Not endorsed by the FAA. Price: 10 sats (Lightning) or $0.01 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"airport_delays","data":{"coverage":"us","source":"faa_nas_status","updated":"2026-11-15T20:00:00Z","counts":{"ground_stops":1,"ground_delays":2,"arrival_departure_delays":1,"closures":1,"airports_affected":5,"events":5},"events":[{"airport":"SFO","type":"ground_delay","reason":"wind"}],"airports":["SFO"],"not_for_navigation":true},"metadata":{"cost_sats":10}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

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": "get_airport_delays"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoAlias of airport.
iataNoAlias of airport.
icaoNoAlias of airport.
airportNoUS airport IATA (SFO) or ICAO (KSFO) code. Required for get_travel_airport; optional filter for get_airport_delays.
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.",
      +  "type": "string"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description goes well beyond them by disclosing paid access, both payment rails, the exact 402 retry mechanics (L402 macaroon:preimage, x402 PAYMENT-SIGNATURE/X-PAYMENT headers, 'only a 200 is settled'), and a sample payload. That is precisely the behavioral context an agent cannot get from the structured fields, and it does not conflict with readOnlyHint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The opening sentence is well front-loaded and earns its place, but the middle is dominated by a ~350-character illustrative JSON blob that is mostly boilerplate and duplicated by the envelope concepts. The payment paragraph repeats mechanics the schema parameters already describe, so the text is longer than the information content warrants.

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?

With no output schema, the sample payload supplies the return shape an agent otherwise could not infer, and the payment flow covers the one non-obvious prerequisite of actually calling a paid endpoint. All six optional parameters are documented, so an agent has everything needed to invoke it correctly on first or retry attempt.

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% and each parameter already explains itself, including the airport alias set and both payment credential formats, so the baseline is 3. The description's 'optional airport=SFO' and retry-header prose restate what the schema already documents rather than adding new meaning.

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 and scope: US airport ground stops, delay programs, arrival/departure delays and closures sourced from the FAA NAS Status snapshot. It also carries two exclusions ('Not for navigation', 'Not endorsed by the FAA'). It stops short of naming a sibling such as get_travel_airport as an alternative, leaving that routing to 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 Guidelines3/5

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

Usage guidance is implied rather than stated: the agent learns the tool returns FAA status data and that airport is only an optional filter ('optional airport=SFO'), but nothing tells it when this tool beats get_travel_airport or any other sibling. The 'Not for navigation' line is a genuine when-not, which lifts it above a bare 2.

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