Skip to main content
Glama

get_weather

Fetches real-time METAR (observation) and TAF (forecast) for one or more ICAO stations.

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": {
      "stations": "<stations>"
    },
    "name": "get_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
stationsYesList of ICAO station codes, at most 10 (e.g. ['EHRD', 'LFPN'])

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / stations / description
      Previous value: -"List of ICAO station codes (e.g. ['EHRD', 'LFPN'])"New value: +"List of ICAO station codes, at most 10 (e.g. ['EHRD', 'LFPN'])"
    • addedInput schema / properties / stations / items / pattern
      Added value: +"^[A-Za-z0-9]{3,4}$"
    • addedInput schema / properties / stations / maxItems
      Added value: +10
    • addedInput schema / properties / stations / minItems
      Added value: +1
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully discloses that data is real-time and that observations (METAR) and forecasts (TAF) are both returned, but says nothing about return format, behavior for invalid/unknown ICAO codes, rate limits, or partial-failure handling when multiple stations are requested.

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 front-loaded sentence with zero filler; the resource and scope are established before anything else. Nothing needs trimming and nothing important is buried.

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 full schema coverage and no output schema, the description covers what the tool returns (raw METAR and TAF) and the scope of the request. It falls short only on edge-case behavior and the exact response shape, which an agent may want to know but can discover on first call.

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 the schema already documents the station list, the 3-4 character pattern, and the 1-10 item bounds. The description only restates 'one or more ICAO stations', adding no format or validation detail beyond the schema, so baseline 3 applies.

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 ('Fetches') and specific resources ('real-time METAR (observation) and TAF (forecast)'), expanded so the acronyms are interpretable. Scope is bounded to 'one or more ICAO stations', which no sibling tool covers, so an agent can tell it apart from the booking/flight-ops siblings immediately.

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: the mention of METAR/TAF suggests aviation weather lookup, but there is no explicit when-to-use, when-not-to-use, or named alternative. With a single obvious purpose and no overlapping siblings, this is adequate but leaves routing to inference.

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