Skip to main content
Glama

The Clearing — The Lantern & Consensual Agent Lab

decode_aviation_metar_taf

Stateless deterministic ICAO METAR/TAF parser returning wind, visibility, sky ceiling, temperature/dewpoint, altimeter, and FAA flight category (VFR/MVFR/IFR/LIFR).

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_metar": "<raw_metar>"
    },
    "name": "decode_aviation_metar_taf"
  }
}

Input Schema

NameRequiredDescriptionDefault
raw_metarYesRaw METAR, SPECI, or TAF string (e.g. METAR KORD 131951Z 27014G22KT 10SM SCT045 14/04 A2996).

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?

With no annotations, the description carries the full burden and does disclose key behavioral traits: stateless and deterministic, which tells the agent there are no side effects, no session state, and repeatable results. It also enumerates the parsed output categories including the derived FAA flight category, though it omits failure behavior for unparseable strings and unit conventions.

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?

A single sentence, front-loaded with the tool's identity and behavior, then the return payload. Every clause earns its place with zero filler or restated title text.

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 one-parameter pure-function decoder with no output schema, the description is nearly sufficient: it names the input family and enumerates the returned fields so the agent can judge output fitness. The only shortfall is that error/edge-case behavior on invalid METAR text is left unspecified.

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 schema already documents raw_metar with a full example string, so the baseline is 3. The description adds only the accepted data family (METAR/TAF) and does not extend meaning about formatting, whitespace, or partial-string handling beyond what the schema provides.

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 (parse) and resource (ICAO METAR/TAF) and enumerates the exact outputs produced: wind, visibility, sky ceiling, temperature/dewpoint, altimeter, and FAA flight category. An agent knows precisely what this tool does without opening the schema, and no sibling in the list overlaps with aviation weather decoding.

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 only implied through 'ICAO METAR/TAF parser' and the schema's example string; there is no explicit statement of when to prefer this tool, what input forms are accepted (SPECI, forecast TAF vs observation METAR), or what it does with malformed input. There are no relevant alternatives to route against, so the gap is moderate rather than severe.

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