Skip to main content
Glama

Current weather + forecast for a location

get_weather
Read-only

Retrieves current MeteoSwiss conditions, an 8-day forecast and active weather warnings for a 4-digit Swiss postal code.

Instructions

MeteoSwiss current conditions, 8-day forecast and active weather warnings for a Swiss postal code (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"
  }
}

Input Schema

NameRequiredDescriptionDefault
plzYes4-digit Swiss postal code, e.g. '8001' for Zürich

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine context beyond them: the upstream data source, the 8-day forecast horizon, that active warnings are included in the same response, and the geographic constraint to Switzerland (postal codes only). It does not cover units, language, or empty-warning behavior.

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?

One dense sentence, front-loaded with the provider and resource, with every clause contributing required information (source, forecast length, warnings, geography). No filler or redundancy.

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 no output schema, the description conveys what comes back (current conditions, 8-day forecast, warnings) and the geographic limit, which is sufficient to call it correctly. Minor gaps remain around response format and units, but nothing critical is missing.

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%: the single parameter already carries the 4-digit pattern and a Zürich example. The description only restates that it is a Swiss postal code, adding no format or edge-case detail beyond the schema, so the baseline of 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?

The description names the provider (MeteoSwiss), the exact bundle returned (current conditions, 8-day forecast, active warnings), and the required input shape (Swiss postal code). This is specific enough that an agent can distinguish it from forecast-only or warning-only siblings, even though none are named explicitly.

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 bundled nature of the result suggests this is the general-purpose weather lookup and that separate warning/history calls may be unnecessary. There is no explicit when-to-use or when-not-to-use statement, and 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