Tanod MCP server

skypeek: decode a METAR or TAF report

decode_metar_taf

Read-onlyIdempotent

Decode METAR or TAF weather reports into wind, visibility, weather, clouds, temperature, altimeter, and flight category. Paste raw text; unrecognized groups are listed separately.

Instructions

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

Input Schema

TableJSON Schema

Name	Required	Description	Default
`raw`	Yes	One METAR or TAF report as text (at most 2,000 characters).
`kind`	No	Report type; auto detects it.	auto

Output Schema

TableJSON Schema

Name	Required	Description
`kind`	No
`note`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`decoded`	No
`disclaimer`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already cover the read-only/idempotent/non-destructive profile, and the description adds substantial context beyond them: decoded output groups, unrecognised groups surfaced in `unparsed`, day/hour-as-reported with no month/year, the 422 invalid_report path (not charged), no upstream call, sub-0.1s latency, pricing and free tier.

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?

Dense and front-loaded—the core action and routing lead, then behavior, limits, and pricing. Every sentence carries information, though the pricing/free-tier/docs tail is longer than strictly needed for tool selection.

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?

An output schema exists, yet the description still summarizes what comes back (wind, visibility, clouds, temperature, flight category, TAF periods) and flags the unparsed buffer and error path, leaving no gap for a text-in/structured-out decoder.

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 with its 2,000-char cap, kind enum with auto default) are documented in the schema. The description implies the paste-and-decode flow and the METAR/TAF distinction but adds no syntax or kind-detection detail beyond the schema, so the baseline 3 holds.

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 (decode) and resource (METAR or TAF weather report) and names the sibling get_metar for the fetch case. An agent can immediately distinguish it from get_metar/get_taf without opening the schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: fetch the latest report with get_metar, use this to decode text you already have. Also states a when-not ('Informational only: not for flight planning or navigation'), covering both the alternative and the exclusion.

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

Deploy Server