Skip to main content
Glama

Aviation & Space Weather Data (Tanod)

decode_metar_taf

Read-onlyIdempotent

skypeek: Decode a METAR or TAF weather report. To fetch the latest report use get_metar. Returns one METAR or TAF report you paste, decoded into wind, visibility, weather, clouds, temperature and dew point, altimeter and the flight category (VFR / MVFR / IFR / LIFR) (TAF: each forecast period and the temperature extremes); groups it does not recognise are listed in unparsed. Informational only: not for flight planning or navigation. Decoded locally (no upstream call). Day and hour are as reported (UTC); a METAR or TAF carries no month or year. A report it cannot read is a 422 invalid_report (not charged). Typically under 0.1 s. Price: USD 0.001. Free: 5 skypeek calls per IP per UTC day. Docs: https://tanod.dev/learn/decode-metar-taf-api.html

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": {
      "raw": "<raw>"
    },
    "name": "decode_metar_taf"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawYesOne METAR or TAF report as text (at most 2,000 characters).
kindNoReport type; auto detects it.auto

Output Schema

NameRequiredDescriptionDefault
kindNo
noteNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
decodedNo
disclaimerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / kind / title
      Removed value: -"Kind"
    • removedInput schema / properties / raw / title
      Removed value: -"Raw"
    • removedInput schema / title
      Removed value: -"decode_metar_tafArguments"
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "decoded": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "disclaimer": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "kind": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds real context beyond them: decoding happens locally with no upstream call, unreadable input returns a 422 invalid_report that is not charged, pricing and a 5-calls-per-IP-per-day free tier, sub-0.1s latency, and the UTC day/hour limitation with no month or year. It even says what happens to unrecognised groups (surfaced in `unparsed`), which is not derivable from the annotations.

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?

The core purpose and the get_metar alternative are front-loaded, and the trailing pricing, latency, error and docs lines are each individually useful. It is dense for a two-parameter tool and the docs URL plus price/free-quota clause add bulk, but nothing is genuinely redundant.

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?

Despite having an output schema, the description still sketches the return shape (wind, visibility, weather, clouds, temperature, altimeter, flight category, forecast periods, `unparsed`), and it covers failure mode, cost, and latency. For a simple two-param read-only decoder, an agent has everything needed to call and interpret it.

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 (`raw`, `kind`) are documented in-schema, including the enum and the auto-detect default. The description reinforces that exactly one report is expected and that it must be pasted text, but adds no format examples or guidance beyond the schema.

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 and resource ("Decode a METAR or TAF weather report") and enumerates the decoded outputs, so an agent knows exactly what transformation happens. It also distinguishes itself from the sibling get_metar by noting that this tool decodes text you paste rather than fetching the latest report.

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?

Explicitly routes the agent to get_metar when the goal is fetching the latest report, which is a genuine alternative-selection rule. It also carries a "not for flight planning or navigation" caveat, though that reads more as a disclaimer than a selection guideline; there is no explicit statement about when a pasted report is the wrong input.

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.