Skip to main content
Glama

List IMIS snow stations

list_snow_stations
Read-only

Retrieve SLF IMIS high-alpine snow measurement stations with codes, names, elevation and coordinates; filter by canton or name, or sort by distance from a point.

Instructions

List SLF IMIS high-alpine measurement stations with code, name, elevation and coordinates. Filter by canton or name, or sort by distance from a point.

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
limitNo
queryNoName fragment filter
cantonNoCanton code filter, e.g. 'GR', 'VS'
near_latNo
near_lonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/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. Beyond that the description only adds the shape of returned records; it says nothing about the default result cap (limit=25, max 100), whether results are truncated silently, or how distance sorting is ordered/unitized.

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 compact sentences with zero filler, leading with what the tool returns and following with the available filtering/sorting modes. Every clause carries information an agent would otherwise have to guess.

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 read-only listing tool with no output schema, the description covers returned fields and filtering modes well enough to call it correctly. The remaining gap is result-set behavior: the 25/100 limit semantics and distance-sort ordering are left entirely to inference.

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?

Schema coverage is only 40%, with limit, near_lat and near_lon undocumented in the schema, so the description must compensate. It does partially: 'sort by distance from a point' explains the near_lat/near_lon pair's purpose and 'query' is confirmed as a name filter, though limit and any ordering rules remain unexplained.

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?

Names a specific verb and resource (SLF IMIS high-alpine measurement stations) and enumerates the returned fields (code, name, elevation, coordinates). The 'IMIS high-alpine' qualifier implicitly distinguishes it from generic weather/air-quality station lists, but it never names a sibling or clarifies its relationship to get_nearby_stations or search_stations.

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 says 'filter by canton or name, or sort by distance from a point', which tells the agent what kinds of queries are supported but not when to pick this over get_nearby_stations or search_stations. Usage is implied through the filter vocabulary rather than stated as explicit selection criteria or exclusions.

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