Skip to main content
Glama

get_snow_conditions

Read-onlyIdempotent

Check current snow depth and 24-hour new snow at SLF IMIS stations, sorted deepest first; filter by canton, minimum altitude, or result limit to find relevant conditions.

Instructions

Current snow depth and 24h new snow at SLF IMIS stations, deepest first

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": "get_snow_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNomax 100
cantonNoCanton code, e.g. GR
min_altitudeNoMetres

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, UR, TI). 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: 100)."New value: +"max 100"
    • changedInput schema / properties / min_altitude / description
      Previous value: -"Minimum station altitude in metres (e.g. 2000). Optional."New value: +"Metres"
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the upstream network (SLF IMIS), the snapshot currency, and the sort order. It does not disclose pagination/truncation behavior or that only a top-N slice is returned by default, which matters for a ranked list.

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 compact sentence with the returned measures, the source, and the ordering front-loaded. There is no padding or redundant restatement of the tool name.

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?

All parameters are optional and the description identifies the returned quantities and sort order, which is a lot of what an agent needs. Gaps remain for a tool with no output schema: units of snow depth (cm vs m), whether station name/altitude/canton accompany each record, and how many results the default limit yields.

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 three parameters (limit, canton, min_altitude) are already documented with defaults, the max of 100, and units in metres. The description adds nothing about how filtering interacts with the 'deepest first' ranking, so it sits at the schema-driven baseline.

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 names a specific resource (current snow depth plus 24h new snow), the data source (SLF IMIS stations), and the ordering (deepest first), so an agent knows exactly what comes back. It stops short of naming the closest siblings (get_snow_measurements, list_snow_stations), so the differentiation from those is only implicit in the word 'current'.

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?

Usage is implied rather than stated: 'current' plus 'deepest first' signals a ranked snapshot of present conditions, as opposed to a per-station history. There is no explicit when-to-use/when-not guidance and no routing to get_snow_measurements or list_snow_stations, which an agent would likely confuse this with.

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