Skip to main content
Glama
cuolm

meteo-swiss-mcp

by cuolm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

daily_forecast

Get whole-day weather forecasts for any Swiss location, including daily temperature lows and highs, rainfall, and conditions. Plan one day or several days ahead.

Instructions

        Get the whole-day forecast for a location, 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): Location name (e.g., "Zurich") or Swiss postal code (e.g., "8001").
            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 resolved location with its altitude, one row per day, and the model run.
                Each row has the date and weekday, the minimum and maximum temperature in
                Celsius, the day's rainfall in millimetres as its median and its 10th and 90th
                percentile (in 8 of 10 possible outcomes, the rain lies between the two
                percentiles), and the weather in words with a matching emoji. A value is None
                when MeteoSwiss does not publish it for that location.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo
locationYes
start_dateYes

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 it delivers richly: it defines the Swiss calendar day boundary (00:00–24:00), clarifies that min/max are hourly mean temperatures, states the weather words describe daytime, and explains that values can be None when MeteoSwiss does not publish them. This goes far beyond a generic 'get forecast' statement.

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-organized with Args, Returns, and Examples sections. It is detailed but every sentence adds needed information about semantics, constraints, or output interpretation, especially given that no annotations and no output schema exist to supplement it.

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?

The tool has no output schema, so the description must cover return values, and it does thoroughly: the resolved location, altitude, per-day rows, model run, temperature min/max, rainfall percentiles, weather words, and None semantics. Considering the moderate complexity and the absence of structured metadata, the description is complete enough for correct invocation.

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?

The input schema provides zero parameter descriptions (0% coverage), so the description must compensate. It fully does so by giving formats ('ISO 8601', e.g. '2026-09-23'), valid ranges ('today or up to 8 days ahead', 'days from 1 to 9'), a default ('Default 1'), and concrete examples for both location and days.

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 states a specific verb and resource: 'Get the whole-day forecast for a location, for one day or several days in a row.' It clearly differentiates from siblings like hourly_forecast by framing itself as the day-level view and explicitly notes it is the 'cheapest way' to answer daily weather questions and 'Always use this for the rain of a whole day.'

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 gives clear context for when to use this tool: for a day, weekend, or week, and specifically for whole-day rainfall. It does not explicitly name sibling alternatives and say 'use hourly_forecast instead when...', but the 'always use this for the rain of a whole day' guidance and the day-level framing strongly imply the boundary versus other forecast tools.

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