Skip to main content
Glama

list_snow_stations

Retrieve Swiss snow measurement station data including location, altitude, and type. Filter by canton or station type to access SLF automatic and manual snow monitoring information.

Instructions

List all SLF snow measurement stations in Switzerland (IMIS automatic stations and manual study plots). Returns station code, name, altitude, canton, and type. Sorted by elevation descending.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cantonNoFilter by canton abbreviation (e.g. GR, VS, BE). Optional.
typeNoStation type: "imis" (automatic) or "study-plot" (manual). Optional — returns both by default.
limitNoMaximum number of stations to return (default: 20, max: 200).

Implementation Reference

  • Handler function for the 'list_snow_stations' tool. It fetches station data from IMIS and study plots, merges, filters, and formats the result.
    async function handleListSnowStations(
      args: Record<string, unknown>
    ): Promise<string> {
      const canton = typeof args.canton === "string" ? args.canton.trim().toUpperCase() : undefined;
      const typeFilter = typeof args.type === "string" ? args.type.trim().toLowerCase() : undefined;
      const limit = Math.min(Math.max(Number(args.limit) || 20, 1), 200);
    
      // Fetch station lists (conditionally based on type filter)
      const fetchImis = !typeFilter || typeFilter === "imis";
      const fetchStudy = !typeFilter || typeFilter === "study-plot";
    
      const [imisStations, studyStations] = await Promise.all([
        fetchImis ? fetchJSON<ImisStation[]>(`${BASE}/imis/stations`) : Promise.resolve([]),
        fetchStudy ? fetchJSON<StudyPlotStation[]>(`${BASE}/study-plot/stations`) : Promise.resolve([]),
      ]);
    
      type StationEntry = {
        code: string;
        name: string;
        altitude_m: number;
        canton: string;
        type: string;
      };
    
      const combined: StationEntry[] = [
        ...imisStations.map((s) => ({
          code: s.code,
          name: s.label,
          altitude_m: s.elevation,
          canton: s.canton_code,
          type: "imis" as const,
        })),
        ...studyStations.map((s) => ({
          code: s.code,
          name: s.label,
          altitude_m: s.elevation,
          canton: s.canton_code,
          type: "study-plot" as const,
        })),
      ];
    
      const filtered = combined
        .filter((s) => !canton || s.canton === canton)
        .sort((a, b) => b.altitude_m - a.altitude_m)
        .slice(0, limit);
    
      return JSON.stringify({
        count: filtered.length,
        total_stations: combined.length,
        ...(canton ? { canton } : {}),
        ...(typeFilter ? { type: typeFilter } : {}),
        stations: filtered,
        source: "WSL Institute for Snow and Avalanche Research SLF (CC BY 4.0)",
      });
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses return fields (station code, name, altitude, canton, type) and sorting behavior, but lacks information about permissions, rate limits, pagination, or error conditions. For a read-only list tool, this is minimally adequate but misses important operational context.

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?

Two sentences with zero waste. First sentence defines purpose and scope, second specifies return fields and sorting. Every word earns its place, and key information is front-loaded.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple list tool with no output schema, the description provides good context about what's returned and how it's sorted. However, without annotations or output schema, it lacks information about response format, error handling, or operational constraints. The completeness is good but not comprehensive.

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 100%, so the schema fully documents all three parameters. The description adds no parameter-specific information beyond what's in the schema. The baseline score of 3 reflects adequate coverage through the schema alone, with no additional value from the description.

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 clearly states the verb ('List') and resource ('SLF snow measurement stations in Switzerland'), specifying scope (IMIS automatic stations and manual study plots). It distinguishes from siblings like 'get_snow_conditions' or 'get_snow_measurements' by focusing on station metadata rather than weather data or measurements.

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?

The description implies usage for retrieving station lists, but provides no explicit guidance on when to use this tool versus alternatives like 'list_weather_stations' or 'get_nearby_stations'. It mentions sorting by elevation descending, which gives some context, but lacks explicit when/when-not statements or named alternatives.

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