Skip to main content
Glama
Sign In
cuolm

meteo-swiss-mcp

by cuolm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

forecast_wind

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

Instructions

        Get the wind at a place 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): Place name: a town, village, city district, lake or peak (e.g., "Zurich").
            when (str): Swiss local time as a full hour in ISO 8601 without offset, e.g. "2026-09-23T14:00". Today or up to 8 days ahead.

        Returns:
            dict: The wind, the place, the forecast point used, the time it is valid for and the
                model run; the field names give the units.

        Examples:
            forecast_wind("Zurich", "2026-09-23T14:00")
            forecast_wind("Titlis", "2026-09-24T12:00")

Input Schema

NameRequiredDescriptionDefault
nearNoOnly when several places share the name: a village next to the place the user means. For "the Blausee near Bettmeralp" use location "Blausee" and near "Bettmeralp". Leave it out otherwise.
whenYes
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it explains that speed is the hourly mean, gust is the strongest one-second gust in that hour, and the 90th percentile is a cautious estimate rather than the maximum possible gust. It also describes the direction convention and the general return contents, though it does not explicitly state that the operation is read-only or mention any access constraints.

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 front-loaded with the tool purpose, then organized into semantics, Args, Returns, and Examples. The extra detail on gust percentile and direction convention is useful for correct interpretation, and no sentence is redundant.

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 forecast tool with no output schema and no annotations, the description is mostly complete: it explains the output dict contents, time validity, location types, and examples. The main omission is any mention of the optional near parameter for disambiguating shared place names, although that parameter is described in the schema.

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 only 33%, so the description must compensate for undocumented parameters. It adds strong meaning for location and when, including place types, Swiss local time format, full-hour requirement, and forecast horizon, but it never mentions the optional near parameter, which is documented only in the schema.

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 gives a specific verb and resource: get wind at a place and time, including mean speed, strongest gust, and direction. It is clearly distinct from sibling forecast tools by variable, but it does not explicitly contrast itself with alternatives such as forecast_hourly or current_conditions.

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?

The time window and location expectations provide implied usage context, but the description never states when to choose forecast_wind over sibling tools such as forecast_hourly or current_conditions. There are no explicit when-not conditions or alternative-routing guidance.

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