Skip to main content
Glama

Live measurements from MeteoSwiss stations

get_current_measurements
Read-only

Retrieve live 10-minute SwissMetNet measurements from MeteoSwiss by parameter, and filter stations by proximity or name to get current local weather data.

Instructions

Live 10-minute measurements from the official MeteoSwiss (SwissMetNet) station network. Choose a parameter and optionally filter to stations near a point (pass both near_lat and near_lon) or by name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parameter": "<parameter>"
    },
    "name": "get_current_measurements"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
near_latNoOptional: WGS84 latitude to sort stations by distance (requires near_lon)
near_lonNoOptional: WGS84 longitude (requires near_lat)
parameterYesMeasured parameter
station_nameNoOptional: filter by station name fragment

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and openness are covered. The description adds meaningful context beyond that: the data is 'live' and refreshed on a 10-minute cadence, and comes from an authoritative official network. It does not explain sorting behavior when near coordinates are supplied, what happens for a station/parameter combination with no data, or whether historical values are included.

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?

Two sentences, front-loaded with the data source and freshness, followed by the filtering options. There is little waste; only the generic lead-in 'Choose a parameter' could be trimmed.

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

Completeness3/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 is the only place an agent could learn what comes back, and it never states the return shape (station identifiers, measurement values, units, timestamps) or how results are ordered. Given a 5-parameter tool with a single required enum, the description is adequate to invoke it but not complete enough to anticipate the response.

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 80%, so the baseline is 3. The description's filter hints (both near coordinates required, or filter by name) largely restate what the schema already documents in the near_lat/near_lon/station_name descriptions, and it adds no detail on limit semantics or the enum choices.

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 names a specific resource (live 10-minute measurements) and a specific source (official MeteoSwiss / SwissMetNet station network), so an agent knows exactly what data it returns. It does not differentiate itself from sibling station-discovery tools such as get_nearby_stations, list_weather_stations, or search_stations, leaving some ambiguity about which tool serves which need.

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?

It gives clear invocation guidance for the optional filters, including the important constraint that near_lat and near_lon must be supplied together, and that station_name is an alternative filter. It says nothing about when this tool should be chosen over sibling tools (e.g., finding stations versus reading measurements from them), so usage relative to alternatives is only implied.

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