Skip to main content
Glama

Airport Report - live flights, delays, weather and airport data

airport_report
Read-onlyIdempotent

One call for one airport: airport record (IATA/ICAO, location, time zone), planes arriving and departing right now with airline and route, FAA delays and delay risk for US airports, METAR/TAF weather elsewhere. ~1-3 s. Free: 25 calls/day per IP. Paid: $0.01 per call via x402 at https://radarbg.com/x402/airport-report.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "airport": "JFK",
      "maxFlights": 10
    },
    "name": "airport_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportYesIATA or ICAO code, e.g. JFK or EGLL
maxFlightsNoMax live flights

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds genuinely useful non-schema facts: ~1-3 s latency, a free tier of 25 calls/day per IP, paid pricing at $0.01/call, and the x402 payment endpoint. It does not state error behavior for unknown airport codes, which keeps it short of a 5.

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?

Three compact sentences with zero filler: payload contents first, then latency, then cost/quota. Every clause carries distinct information and there is no repetition of the title or schema.

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 read-only open-world aggregation tool with no output schema, the description covers what comes back, how fresh it is, what it costs, and the throttling limit. The main remaining gap is undefined behavior for invalid or unsupported airport codes and whether US-only data is absent rather than empty for non-US airports.

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% and both parameters (airport code format, maxFlights with min/max/default) are documented in the schema itself. The description's only added semantic is the 'one airport per call' scoping, so baseline 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?

The description names the exact resource ('one airport') and enumerates the four data families returned: airport record with IATA/ICAO and time zone, live arrivals/departures with airline and route, FAA delays/risk for US airports, and METAR/TAF weather elsewhere. That specificity makes it clearly distinguishable from the sibling tools, which are all domain/web/security lookups.

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 phrase 'One call for one airport' implies a single-airport-per-call usage pattern and hints that this bundles data you'd otherwise fetch separately, but there is no explicit when-to-use guidance, no exclusions, and no comparison to alternatives for weather or delay data.

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