Skip to main content
Glama

List MeteoSwiss measurement stations

list_weather_stations
Read-only

List official SwissMetNet weather stations reporting a chosen parameter such as temperature, precipitation, wind, humidity or sunshine, including coordinates and altitude for mapping and site selection.

Instructions

List official SwissMetNet stations reporting a given parameter, with coordinates and altitude.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_weather_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
parameterNotemperature

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.3/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 the safety profile is covered. The description adds useful return-shape context (coordinates and altitude) but says nothing about whether the list is exhaustive, whether only currently-reporting stations appear, or how results are ordered.

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?

A single front-loaded sentence with no filler; the resource, the filter, and the returned fields all appear in the first clause. Nothing is wasted or buried.

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?

For a one-parameter read-only listing with no output schema, the description covers the essential contract and the returned fields. It stops short of the details an agent would want before calling, such as the result set size, ordering, or whether stations lacking the chosen parameter are excluded.

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 0%, but there is only one parameter and its five enum values are self-explanatory. The description clarifies that the parameter filters which stations are returned, yet omits the documented default of "temperature" and what happens for parameters with sparse coverage.

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 ("List") and resource ("official SwissMetNet stations") plus the scope qualifier "reporting a given parameter" and the returned fields. The SwissMetNet/weather framing separates it from list_hydro_stations and list_air_quality_stations, though it never explicitly contrasts itself with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no exclusions, and no pointer to alternatives such as get_nearby_stations or search_stations for proximity or name-based lookups. The agent must infer from the single sentence that this is a parameter-filtered inventory listing.

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