Skip to main content
Glama

airport_weather

Fetches an airport’s latest METAR and TAF plus impact flags, helping agents assess weather conditions without credentials or OpenSky credits.

Instructions

Return the latest METAR and TAF for an airport, plus impact flags.

Needs no credentials and spends no OpenSky credits.

Args:
    airport: ICAO code, e.g. ESGG.

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": {
      "airport": "<airport>"
    },
    "name": "airport_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
airportYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description usefully discloses that no credentials are needed and no OpenSky credits are spent. It does not cover other behavioral details such as freshness, rate limits, or error behavior, though the output schema reduces the need to explain return values.

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?

The description is front-loaded and concise, with three short sections covering purpose, cost/auth behavior, and the input parameter. Every sentence adds useful information without padding.

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 read tool with an output schema, the description covers purpose, auth/cost context, and the input format. The main gap is the absence of explicit guidance versus sibling tools, which keeps it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry parameter meaning, and it does: the single airport parameter is identified as an ICAO code with an example (ESGG). That fully clarifies the only input beyond the bare schema.

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 states a specific verb and resource: return latest METAR and TAF for an airport, plus impact flags. This clearly separates it from sibling tools about traffic, movements, or triage, though it does not explicitly name those alternatives.

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

Usage Guidelines2/5

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

It implies the tool is for airport weather retrieval but gives no explicit when-to-use guidance, prerequisites, or comparison to sibling tools. An agent must infer its role from the resource alone.

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