Skip to main content
Glama
cuolm

meteo-swiss-mcp

by cuolm

current_conditions

Get the latest measurements of a MeteoSwiss station near the location.

Instructions

        Get the latest measurements of a MeteoSwiss station near the location.

        These are the measurements of that station, not of the location itself. The station is
        the one with the smallest distance plus 20 times the height gap, so it can be several
        kilometres away and hundreds of metres higher or lower than the location. Always start
        the answer with the data_from sentence, which names the station, its distance and its
        height difference, and then give the values as the station's measurements. MeteoSwiss
        publishes new values about every 10 minutes.

        Temperature, humidity, dew point and pressure are measured at measured_at. Rain,
        sunshine, wind speed, the strongest gust and the wind direction cover the 10 minutes up
        to it. The temperature and pressure changes compare measured_at with 3 hours before it,
        negative when the value fell. The rain and sunshine of the last hour are the totals of
        its six 10-minute values, and the strongest gust of the last hour is the highest of them.
        For later today or the coming days use forecast_hourly or forecast_daily.

        Args:
            location (str): Place name: a town, village, city district, lake or peak (e.g., "Zurich").

        Returns:
            dict: The place, the station with its distance and height difference, the time of the
                measurements and the measured values; the field names give the units. A value is
                None when the station does not measure it, and a change or a last-hour value is
                None when the station has not published all the measurements it needs, such as
                shortly after midnight UTC.

        Examples:
            current_conditions("Zurich")
            current_conditions("Braunwald")
        

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.
locationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: station selection uses smallest distance plus 20 times height gap, the station may be kilometres away and hundreds of metres higher or lower, values update about every 10 minutes, and the measured_at and 10-minute window semantics are explained. It also explains when values can be None.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but front-loaded and every paragraph carries relevant semantics for a tool whose measurements are easy to misinterpret. Some repetition about station measurements could be trimmed, but overall the structure is purposeful and efficient.

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?

There is no output schema, so the description must explain return values, and it does: it names the place, station distance and height difference, measurement time and values, with field names giving units. It also defines None cases for missing measurements and for changes or last-hour values that cannot be computed yet.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, but the description compensates for the undocumented location parameter by defining it as a town, village, city district, lake or peak and giving examples. The near parameter is not mentioned in the description, but its schema description is already detailed and sufficient.

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: latest measurements from a MeteoSwiss station near a location. It explicitly distinguishes the tool from forecast siblings by directing later-today and multi-day queries to forecast_hourly or forecast_daily.

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?

It gives an explicit routing rule: use forecast_hourly or forecast_daily for later today or the coming days. It also includes a mandatory answer-format instruction: always begin with the data_from sentence. There is no ambiguity about when this tool is the right choice.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.