Skip to main content
Glama

Current airport weather from NOAA Aviation Weather Center

travel_aviationweather_metar_taf
Read-only

Current airport weather from NOAA Aviation Weather Center: latest METAR (observed temperature, dewpoint, wind, visibility, altimeter, flight category) and the TAF forecast text for a 4-letter ICAO airport code. Raw text is included alongside the parsed fields. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "icao": "<icao>"
    },
    "name": "travel_aviationweather_metar_taf"
  }
}

Input Schema

NameRequiredDescriptionDefault
icaoYes4-letter ICAO airport code, e.g. KJFK, EGLL, LFPG

Output Schema

NameRequiredDescriptionDefault
tafNo
icaoNo
nameNo
metarNo
sourceNo
checkedAtNo
observedAtNo

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 readOnlyHint=true and openWorldHint=true, so the description's added value is the commercial and response-shape context: $0.002 per successful call via x402, failed calls not charged, and raw text returned alongside parsed fields. That is genuine behavioral information an agent would not get from structured fields. It does not discuss rate limits, latency, or data freshness/staleness windows, so it is not 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.

Conciseness4/5

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

One front-loaded sentence identifies the source and payload fields, followed by a short clause on raw text and a pricing note. The pricing sentence is long-ish but directly relevant to invocation decisions. No filler or redundancy.

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 an output schema present, the description does not need to enumerate return values, and it still summarizes the key parsed fields. A single required parameter and read-only annotations make this a low-complexity tool. Minor gap: no note on observation age or update cadence, which matters for weather data.

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 the single parameter already documents the 4-letter ICAO format with examples. The description's mention of a 4-letter ICAO code restates the schema rather than adding new syntax or constraints. Baseline 3 is correct when the schema carries parameter 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 source: latest METAR observations (temperature, dewpoint, wind, visibility, altimeter, flight category) plus TAF forecast text for a 4-letter ICAO code. That is far more precise than a name restatement. It stops short of naming a sibling to contrast with (e.g. flight-tracking tools), so it lands at 4 rather than 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 by the content — an agent can infer this is for current airport weather rather than live flight positions — and the ICAO-code requirement is stated. However, there is no explicit when-to-use vs. when-not guidance and no stated alternatives among the travel tools.

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