Skip to main content
Glama

list_snow_stations

Read-onlyIdempotent

Retrieve SLF snow stations, including automatic IMIS and manual study plots, filtered by canton or station type to support snow and avalanche data workflows.

Instructions

List SLF snow stations (IMIS automatic, manual study plots)

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_snow_stations"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOmit for both
limitNomax 200
cantonNoCanton code, e.g. GR

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.9.0
    • changedInput schema / properties / canton / description
      Previous value: -"Filter by canton abbreviation (e.g. GR, VS, BE). Optional."New value: +"Canton code, e.g. GR"
    • addedInput schema / properties / limit / default
      Added value: +20
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of stations to return (default: 20, max: 200)."New value: +"max 200"
    • changedInput schema / properties / type / description
      Previous value: -"Station type: \"imis\" (automatic) or \"study-plot\" (manual). Optional — returns both by default."New value: +"Omit for both"
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds only domain vocabulary (SLF, IMIS) and says nothing about ordering, pagination behavior, or what a returned station entry contains.

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?

A single front-loaded fragment with zero filler; the resource comes first and the qualifier second. It is efficient rather than padded, though the sentence-fragment form leaves no room for the guidance an agent actually needs.

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

Completeness2/5

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

With no output schema, the description is the only place an agent could learn what a station record looks like (identifier, coordinates, measurements available) and whether those IDs feed get_snow_measurements. None of that is present, and the canton-vs-type relationship is left unstated.

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 every parameter (type, limit, canton) is already documented, including 'Omit for both' and 'max 200'. The description's mention of IMIS and study plots loosely reinforces the type enum but adds no syntax or filtering semantics beyond the schema.

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?

States a specific verb and resource ('List SLF snow stations') and disambiguates the two station kinds in parentheses (IMIS automatic, manual study plots), which maps cleanly onto the type enum. It is distinguishable from measurement/bulletin siblings like get_snow_measurements and get_snow_conditions, though it never names 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 and no routing to alternatives such as get_snow_measurements or search_stations. The agent must infer that this is the enumeration step preceding a measurement lookup.

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