Skip to main content
Glama

list_weather_stations

Retrieve a comprehensive list of MeteoSwiss weather stations across Switzerland to access meteorological data sources.

Instructions

List all available MeteoSwiss weather stations in Switzerland

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler logic for the 'list_weather_stations' tool. It fetches station data from the API and formats it using 'compactWeatherStations'.
    case "list_weather_stations": {
      const url = buildUrl(`${BASE}/smn/locations`, { app: "mcp-swiss" });
      const data = await fetchJSON<ApiResponse>(url);
      const payload = (data?.payload ?? {}) as Record<string, StationEntry>;
      const stations = compactWeatherStations(payload);
      return JSON.stringify({ count: Object.keys(stations).length, stations });
    }
  • The tool definition for 'list_weather_stations', including its description and empty input schema.
    {
      name: "list_weather_stations",
      description: "List all available MeteoSwiss weather stations in Switzerland",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Helper function that parses and formats raw weather station data for the 'list_weather_stations' tool.
    function compactWeatherStations(payload: Record<string, StationEntry>): Record<string, string> {
      const result: Record<string, string> = {};
      for (const s of Object.values(payload)) {
        const code = s.details?.id ?? s.name;
        const name = s.details?.name ?? s.name;
        const canton = s.details?.canton;
        result[code] = canton ? `${name} (${canton})` : name;
      }
      return result;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions listing 'all available' stations but does not specify details like pagination, rate limits, data freshness, or output format. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 a single, efficient sentence with no wasted words, clearly front-loading the purpose. It is appropriately sized for a simple list operation with no parameters.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate but lacks details on output behavior (e.g., format, scope of 'all available'). It meets basic needs but could be more informative for an agent to use it effectively.

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?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not add parameter information, which is acceptable since there are no parameters to explain. A baseline of 4 is appropriate for zero-parameter tools.

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 clearly states the action ('List') and resource ('all available MeteoSwiss weather stations in Switzerland'), providing a specific verb+resource combination. However, it does not distinguish itself from sibling tools like 'list_air_quality_stations' or 'list_snow_stations' beyond specifying the type of stations, which is a minor gap in differentiation.

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?

The description offers no guidance on when to use this tool versus alternatives, such as 'get_nearby_stations' or 'search_stations', nor does it mention any prerequisites or exclusions. It simply states what the tool does without contextual usage information.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/vikramgorla/mcp-swiss'

If you have feedback or need assistance with the MCP directory API, please join our Discord server