Skip to main content
Glama

Snow Depth and Snowpack (SNOTEL) MCP

Snowpack by state

snowpack_by_state
Read-onlyIdempotent

Statewide snowpack from every active SNOTEL station in one state: snow water equivalent as a percent of the 30-year median (summed over stations), the median station percent, how many stations report and have snow, the deepest site, and every station with its snow depth, SWE and percent of median, sorted by depth, SWE, percent of median, elevation or name.

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": {
      "state": "<state>"
    },
    "name": "snowpack_by_state"
  }
}

Input Schema

NameRequiredDescriptionDefault
topNoHow many stations to name in the summary. Default 10; the structured list has every station.
sortNoStation order. Default depth (deepest first).
stateYesState code or name: AK, AZ, CA, CO, ID, MT, NV, NM, OR, SD, UT, WA or WY.

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 readOnly, idempotent, openWorld and non-destructive, so the safety bar is low. The description still adds real value by disclosing the computation (percent of 30-year median summed over stations) and the return shape, including that the structured list contains every station while only the top-N appear in the summary — a distinction not visible in the annotations.

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?

It is a single front-loaded sentence that opens with the scope and then the payload, with no filler or restated title. The dense list of metrics is a little long to parse in one pass, but every clause carries information.

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 describing return values, and it does so thoroughly — aggregates, counts, deepest site, and the full per-station list. Only the absence of guidance on sibling tools and on result size/pagination keeps it short of complete.

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% and each parameter already carries its own description, including defaults and the state enum, so the baseline is 3. The description corroborates the sortable fields and the statewide scope but adds no new syntax, format, or constraint beyond what the schema states.

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 concrete resource and scope: 'Statewide snowpack from every active SNOTEL station in one state', and enumerates the aggregates it returns (SWE as percent of 30-year median, median station percent, reporting/snowing counts, deepest site). That clearly separates it from a single-station tool, though it never names the sibling tools it competes with.

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: an agent can infer this is the state-level rollup versus per-station tools, but there is no explicit 'use this when...' rule, no exclusions, and no pointer to snow_depth or snow_depth_history for station-level or historical queries.

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.