Crypto, web, finance and app data tools

US Airport Status (FAA)

airport_status

Live US airport disruptions from the FAA: closures, ground stops, ground delay programs and arrival or departure delays with reason, average and max delay and expected end. Filter by airport code (JFK, LAX).

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_status"
  }
}

Input Schema

Name	Required	Description	Default
`airport`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does well on output content — reason, average and max delay, expected end — and signals real-time data via 'Live', but says nothing about auth requirements, rate limits, caching/staleness, or what happens when an unknown airport code is passed.

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

Conciseness5/5

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

Two sentences, zero filler. The covered disruption types come first, the filtering hint last, so the agent gets the gist immediately.

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?

An output schema exists, so return fields and delays don't need spelling out, and the description correctly focuses on scope and filtering. The one missing piece is optionality/default behavior for the airport parameter and whether unfiltered calls return a national view.

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 0%, so the description must carry the parameter. It adds real meaning by giving the format and examples ('airport code (JFK, LAX)'), which the bare 'string' schema lacks. However, it never states the parameter is optional or that omitting it returns all US airports — the most consequential semantic for a 0-required-param tool.

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 resource (live US airport disruptions from the FAA) and enumerates exactly what it covers: closures, ground stops, ground delay programs, arrival/departure delays. No sibling tool in the list overlaps with aviation status, and the 'Live ... from the FAA' framing makes the data source and freshness unambiguous.

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 only implied: an agent can infer this is the tool for checking current airport disruptions. There is no explicit 'use when' framing, no statement about what happens when no airport is supplied, and no alternatives or exclusions named (e.g., historical delays or non-US airports).

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

All Crypto, web, finance and app data tools 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.

Resources

Need Help?