Skip to main content
Glama
cuolm

meteo-swiss-mcp

by cuolm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

wind

Get wind speed, gust, and direction for any Swiss location and time. The gust's 90th percentile provides a cautious high estimate to assess wind hazard.

Instructions

        Get the wind at a location at a specific time: mean speed, strongest gust and direction.

        The speed is the mean over the hour up to that time, and the gust the strongest
        one-second gust in that hour, which is what makes wind hazardous. The gust's 90th
        percentile is a cautious high estimate of that strongest gust: in 9 of 10 possible
        outcomes the gust stays below it, and in 1 of 10 it is stronger, so it is not the
        highest gust possible. The direction is where the wind blows from, in degrees clockwise
        from north (0 is a north wind, 180 a south wind) and as a compass point.

        Args:
            location (str): Location name (e.g., "Zurich") or Swiss postal code (e.g., "8001").
            when (str): Swiss local time in ISO 8601 without offset, e.g. "2026-09-23T14:00". Today or up to 8 days ahead.

        Returns:
            dict: Wind speed, gust and the gust's 90th percentile in kilometres per hour, the
                direction in degrees and as a compass point such as "SW", the resolved location
                with its altitude, the time it is valid for, and the model run.

        Examples:
            wind("Zurich", "2026-09-23T14:00")
            wind("Säntis", "2026-09-24T12:00")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
whenYes
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so excellently. It explains the averaging period (mean over the hour), the gust definition (one-second gust), the probabilistic meaning of the 90th percentile, and the direction convention (degrees clockwise from north, compass point). This gives the agent insight beyond the bare operation.

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 well-structured with a concise summary, then a detailed explanation of output semantics, followed by Args, Returns, and Examples sections. Every sentence adds value — the probabilistic note and directional convention are important for correct interpretation. It is longer than a bare one-liner but not bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with only two parameters, no output schema, and no annotations, the description is exceptionally complete. It documents parameter formats, constraints, the exact return fields, and gives usage examples. An agent has everything it needs to call this tool correctly and interpret the result.

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 description coverage is 0%, so the description must fully document both parameters. It does: location accepts a place name or Swiss postal code with examples, and when is specified as Swiss local ISO 8601 without offset with constraints (today to 8 days ahead) and an example. This compensates completely for the schema's lack of descriptions.

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?

The description opens with a clear verb and resource: 'Get the wind at a location at a specific time', followed by the specific outputs (mean speed, strongest gust, direction). This is unambiguously distinct from sibling tools like hourly_forecast or rain_outlook, so an agent can identify it without needing to open the schema.

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

Usage Guidelines4/5

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

The description clearly conveys the tool's intended use case — retrieving wind data for a single location at a particular point in time — which is enough to infer when to select it. However, it does not explicitly mention alternatives or provide exclusions, so it falls short of the full explicit-routing bar.

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