Skip to main content
Glama
Sign In
cuolm

meteo-swiss-mcp

by cuolm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

forecast_daily

Get the whole-day forecast for a place, for one day or several days in a row: the cheapest way to answer "how is the weather" for a day, the weekend or the week.

Instructions

        Get the whole-day forecast for a place, for one day or several days in a row: the
        cheapest way to answer "how is the weather" for a day, the weekend or the week.

        Each day covers a Swiss calendar day, 00:00 to 24:00 local time. The minimum and maximum
        are the lowest and highest hourly mean temperature of that day, and the weather words
        describe the daytime. Always use this for the rain of a whole day.

        Args:
            location (str): Place name: a town, village, city district, lake or peak (e.g., "Zurich").
            start_date (str): The first Swiss calendar day in ISO 8601, e.g. "2026-09-23". Today or up to 8 days ahead.
            days (int): How many days in a row, from 1 to 9. Default 1.

        Returns:
            dict: The place, the forecast point used, one row per day and the model run; the
                field names give the units. In 8 of 10 possible outcomes, the day's rain lies
                between its 10th and 90th percentile. A value is None when MeteoSwiss does not
                publish it for that forecast point.

        Examples:
            forecast_daily("Zurich", "2026-09-23")
            forecast_daily("Lugano", "2026-09-26", 2)   # a weekend

Input Schema

NameRequiredDescriptionDefault
daysNo
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.
locationYes
start_dateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A5/5.0
Behavior5/5

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

No annotations exist, and the description carries the full burden well: it defines the Swiss calendar day (00:00-24:00 local), explains how min/max are derived from hourly means, warns that weather words describe the daytime, and discloses uncertainty (rain between the 10th and 90th percentile in 8 of 10 outcomes) and None handling. These are non-obvious behaviors an agent could not get from the schema.

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?

Front-loaded with the core purpose and routing sentence, followed by tightly organized semantics, argument notes, return notes and two concrete examples. Every line adds information; nothing is repetitive padding.

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?

A four-parameter forecast tool with no output schema and no annotations still gets everything an agent needs: input formats, ranges, defaults, return structure and unit conventions, uncertainty interpretation, and null-value behavior. No material gap remains.

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 only 25%, but the description supplies the missing meaning: location accepts towns, districts, lakes or peaks; start_date is an ISO Swiss calendar day from today to 8 days ahead; days is 1-9 with default 1. The only undocumented parameter, `near`, is fully explained in the schema itself.

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?

States a specific verb and resource ("Get the whole-day forecast for a place") and immediately scopes it to one or several consecutive days, which separates it from the hourly and single-variable siblings. The parenthetical "the cheapest way to answer 'how is the weather'" makes the intended use recognizable without opening 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 Guidelines5/5

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

Explicitly routes the agent: use this for a day/weekend/week and "Always use this for the rain of a whole day", which implicitly contrasts with forecast_hourly and the dedicated rain tool. Usage conditions and the date-window limits are stated outright rather than inferred.

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