Airport Weather & Delays (METAR, TAF, FAA)

airport_weather

Check whether weather or US airport delays will affect a flight, pickup or shipment. By ICAO or IATA code: the latest decoded METAR (wind, visibility, ceiling, flight category) and current TAF from the NOAA Aviation Weather Center, FAA ground stops, delay programmes and closures for US airports, and airport details from OurAirports. Use when planning around a specific airport in the next hours. $0.003 per call, USDC on Base (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_weather"
  }
}

Input Schema

Name	Required	Description	Default
`airport`	No	ICAO (EKCH, KJFK) or IATA (CPH, JFK) airport code
`payment_signature`	No	x402 v2 PAYMENT-SIGNATURE header value. Omit to receive payment requirements.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden and does so well: it names the upstream sources (NOAA AWC, FAA, OurAirports), the data freshness expectation, and, critically, the $0.003/call USDC-on-Base x402 payment requirement. It omits failure modes (e.g. what an unknown code returns) but the cost/auth disclosure is the important one.

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-loads purpose, then enumerates data sources, then the usage window and pricing. Dense but each sentence earns its place; only the source list could be slightly trimmed.

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 priced lookup with no output schema, the description covers what is returned, from where, and at what cost. It is complete enough to invoke correctly; the absence of error/empty-result behavior is the only minor 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%, so both parameters are already documented, including the payment_signature omit-to-receive-requirements behavior. The description adds the ICAO/IATA examples context but not much beyond what the schema provides; 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?

States a specific verb (Check) with a precisely enumerated resource set: decoded METAR, TAF, FAA ground stops/delay programmes, and OurAirports details. An agent can tell exactly what data comes back without opening a schema.

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

Usage Guidelines4/5

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

Gives a clear use case (planning around a specific airport in the next hours) and the input form (ICAO/IATA). It doesn't state when NOT to use it or name a preferred alternative, but with no sibling tools the routing burden is low.

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

All Airport Weather & Delays (METAR, TAF, FAA) 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?