Skip to main content
Glama

weather_uae_icao

Read-onlyIdempotent

Get METAR (current weather observation) and optional TAF (forecast) for a UAE airport.

Instructions

Get METAR (current weather observation) and optional TAF (forecast) for a UAE airport.

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": {
      "icao": "<icao>"
    },
    "name": "weather_uae_icao"
  }
}

Input Schema

NameRequiredDescriptionDefault
icaoYesICAO code. Valid: OMDB (Dubai International), OMDW (Al Maktoum), OMSJ (Sharjah), OMAA (Zayed International), OMAL (Al Ain), OMRK (Ras Al Khaimah).
include_tafNoIf True, fetch the TAF forecast as well.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • changedInput schema / properties / icao / description
      Previous value: -"ICAO code. Valid: OMDB (Dubai International), OMDW (Al Maktoum),\nOMSJ (Sharjah), OMAA (Abu Dhabi), OMAL (Al Ain), OMRK (Ras Al Khaimah)."New value: +"ICAO code. Valid: OMDB (Dubai International), OMDW (Al Maktoum),\nOMSJ (Sharjah), OMAA (Zayed International), OMAL (Al Ain),\nOMRK (Ras Al Khaimah)."
  2. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the content distinction between current METAR and forecast TAF, but discloses nothing further (rate limits, coverage gaps, latency) beyond what annotations and schema already convey.

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 primary resource (METAR) precedes the optional one (TAF), matching the call pattern.

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?

An output schema exists, so return values need not be described, and annotations cover safety semantics. The only material gap is routing against sibling weather tools, which is not an invocation-correctness blocker.

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%, including the enumerated valid ICAO codes and the include_taf default, so the schema carries parameter meaning. The description only echoes the optional TAF behavior, adding no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb (Get) and specific resources (METAR current observation, optional TAF forecast) scoped to a UAE airport. An agent understands the tool's output well. However, it does not differentiate itself from the many weather siblings (weather_uae_all, uae_weather, uae_weather_forecast, weather_by_coords), leaving the ICAO-based selection criterion implicit.

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?

No when-to-use or when-not-to-use guidance is given. With at least four sibling weather tools in the list, the agent is left to infer that this one is chosen only when an ICAO code is available and city/coordinate lookups are not. No alternative is named.

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

Deploy Server

Other Tools