Skip to main content
Glama

Official weather warnings for a location

get_weather_warnings
Read-only

Retrieve active MeteoSwiss weather warnings by 4-digit Swiss postal code, including hazard type and danger level 1–5, to assess local weather risks.

Instructions

Active MeteoSwiss weather warnings (wind, thunderstorms, heat, snow, flood, forest fire…) for a Swiss postal code, with danger levels 1–5 (via the MeteoSwiss app service).

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": {
      "plz": "<plz>"
    },
    "name": "get_weather_warnings"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzYes4-digit Swiss postal code

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context beyond that: the upstream source (MeteoSwiss app service) and the 1–5 danger-level scale. It does not say what is returned when no warnings are active, nor how fresh the data is.

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?

One front-loaded sentence with the resource and scope first and the data source in a trailing parenthetical. The hazard list is slightly verbose but conveys real scope information, so nothing is wasted.

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 single-parameter read-only lookup with annotations covering safety and no output schema, the description supplies enough to call it correctly: what it returns (warnings), the scale (1–5), and the geographic constraint. Only the empty-result behavior is left unstated.

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 single parameter is fully documented as a 4-digit Swiss postal code with a regex pattern. The description's 'Swiss postal code' phrasing merely restates the schema, adding no format or edge-case detail, so 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+resource: 'Active MeteoSwiss weather warnings' for a Swiss postal code, and enumerates the hazard categories and danger-level scale. It is clearly distinguishable from a plain forecast tool like get_weather, though it never names a sibling to route against.

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 by the word 'Active' — the agent can infer this is for current warnings rather than forecasts or history, but there is no explicit when-to-use/when-not guidance and no mention of alternatives such as get_weather or get_emergency_alerts.

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