Skip to main content
Glama

Snow Depth and Snowpack (SNOTEL) MCP

Snow depth season history

snow_depth_history
Read-onlyIdempotent

One SNOTEL station's snow season (Oct 1 to Sep 30): daily snow depth, snow water equivalent and the 30-year median SWE, weekly samples, the deepest day and peak SWE so far, first snow, melt-out, the same day last year, last season's peak, and the median onset, peak and melt-out dates. Give a station, or a place to use its nearest station.

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

Input Schema

NameRequiredDescriptionDefault
seasonNoSeason such as "2025-26", or "current" (default) or "last".
stationNoA SNOTEL station name ("Berthoud Summit", "Berthoud Summit, CO"), id ("335") or triplet ("335:CO:SNTL"). Overrides location.
latitudeNoLatitude, with longitude, instead of location.
locationNoA place ("Breckenridge, CO", "Mount Hood", "Alta, UT"), a US ZIP code, or "lat, lon".
longitudeNoLongitude, with latitude.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds substantive output behavior: daily depth/SWE, 30-year median SWE, weekly samples, deepest day, peak SWE, first snow, melt-out, same day last year, and median dates. It doesn't cover errors or rate limits, but the return-content disclosure is strong for a no-output-schema tool.

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?

The description front-loads station and season scope, then packs the return measures into a dense but information-bearing list. It is longer than a simple tool description but avoids filler; the main weakness is that the long enumeration is run-on rather than structured.

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?

With no output schema, the description carries the burden of explaining returns, and it does so across daily, weekly, seasonal, and median climatology outputs. It also explains station vs place input and is sufficient for correct invocation, though units and edge-case behavior are 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 coverage is 100%, so station, location, lat/lon, and season are already documented. The description adds the nearest-station fallback for a place, which is useful beyond the schema, but most parameter meaning remains in 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?

The description identifies the resource as one SNOTEL station's snow season from Oct 1 to Sep 30 and enumerates the season-history measures returned. It doesn't use an explicit verb and doesn't name the sibling snow_depth, but the season/history framing makes the scope distinguishable.

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 only usage instruction is how to supply a station or place; it does not say when to choose this over snow_depth or snowpack_by_state, nor when not to use it. The season-history framing implies the use case, but guidance is implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.