Skip to main content
Glama

Live snow conditions

get_snow_conditions
Read-only

Retrieve current snow depth, temperature, and wind measurements for Swiss IMIS stations; filter by station code or sort by snow depth.

Instructions

Latest measurement per IMIS station (snow depth, temperatures, wind). Filter by station code (from list_snow_stations) or get the deepest-snow stations right now.

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
limitNo
top_snowNoIf true, return stations sorted by current snow depth
station_codeNoIMIS station code, e.g. 'DAV2'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description usefully adds that results are the latest measurement per station rather than a raw series, and that wind/temperature come along with snow depth. It says nothing about result caps, staleness of live IMIS feeds, or failure behavior when a station has no recent data.

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 filler. The core behavior is front-loaded and the alternative invocation mode follows immediately.

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 three-parameter read tool with no output schema, the description covers the resource, the returned fields, and both usage modes. The only real gap is the default result size / limit behavior, which an agent would need to know when scanning stations.

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 coverage is 67%, and the description reinforces station_code's provenance (from list_snow_stations) and top_snow's effect (deepest-snow stations right now). The limit parameter is described nowhere in either the schema or the description, and no units or examples are added beyond what the schema already supplies.

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 and scope: the latest measurement per IMIS station, with the measured fields spelled out (snow depth, temperatures, wind). It partially differentiates itself from the sibling list_snow_stations by citing it as the source of station codes, but it leaves the boundary with other measurement-style siblings (e.g. get_current_measurements) implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Two usage modes are stated directly: filter by station code, or use top_snow to get the deepest-snow stations right now. It also routes the agent to list_snow_stations for valid codes. There is no explicit when-not guidance, but the intended invocation paths are clear.

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