Skip to main content
Glama

get_snow_measurements

Read-onlyIdempotent

Retrieve 30-minute IMIS snow/weather measurements or daily study-plot snow data for a specified SLF station.

Instructions

Measurements for one SLF station: IMIS 30-min snow/weather data, or study-plot daily snow data

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "station_code": "<station_code>"
    },
    "name": "get_snow_measurements"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoimis
station_codeYese.g. DAV2, WFJ2, 4AO0 (see list_snow_stations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.9.0
    • changedInput schema / properties / station_code / description
      Previous value: -"Station code (e.g. DAV2, WFJ2, 4AO0). Use list_snow_stations to find codes."New value: +"e.g. DAV2, WFJ2, 4AO0 (see list_snow_stations)"
    • addedInput schema / properties / type / default
      Added value: +"imis"
    • removedInput schema / properties / type / description
      Removed value: -"Station type: \"imis\" (default) or \"study-plot\". Determines which API endpoint to query."
  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, non-destructive, open-world, so the safety profile is covered. The description adds genuinely new behavioral detail — 30-minute cadence for IMIS versus daily cadence for study-plot — but says nothing about data lag, availability windows, or response shape.

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 dense sentence with the resource front-loaded and the two modes enumerated afterward; nothing is redundant. It reads as a fragment rather than a sentence, but no words are wasted.

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?

With no output schema, the description should hint at what a 'measurement' contains (snow depth, temperature, wind, units). It identifies the two data families but leaves the returned fields opaque, which is a real gap for a data-retrieval tool with two parameters.

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 50%, and the bare `type` enum (imis / study-plot) carries no description in the schema. The description supplies the missing meaning by tying each enum value to a data source and sampling frequency, which is exactly the compensation needed here.

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 concrete resource and scope: measurements for a single SLF station, split into IMIS 30-min snow/weather data and study-plot daily snow data. That is clearly distinct from list_snow_stations (listing) and get_snow_conditions (conditions overview), though it never names those siblings explicitly.

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 only implied: the phrase 'one SLF station' plus the required station_code signals that a station must be picked first, and the schema points to list_snow_stations. There is no explicit statement of when to use this instead of get_snow_conditions or list_snow_stations, and no prerequisites 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