Skip to main content
Glama

Snow Depth and Snowpack (SNOTEL) MCP

Snow depth near a place

snow_depth
Read-onlyIdempotent

Current snow depth (inches and cm), snow water equivalent, SWE as a percent of the 30-year median for the date, and the 24-hour and 7-day change in depth at the SNOTEL stations nearest a place, ZIP code or coordinates, or at a named station. Each station has its elevation and distance. SNOTEL covers the mountains of AK, AZ, CA, CO, ID, MT, NV, NM, OR, SD, UT, WA and WY.

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

Input Schema

NameRequiredDescriptionDefault
countNoHow many nearest stations. Default 3.
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.
max_milesNoSearch radius in miles. Default 60.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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 profile is covered. The description adds real context beyond that: dual units (inches and cm), that each station reports elevation and distance, the median-relative SWE framing, and the geographic coverage limit for SNOTEL. It does not say what an empty result looks like when a location is outside the covered states.

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, both dense: the first front-loads the returned quantities and the accepted locators, the second handles per-station attributes and the coverage caveat. No filler and nothing important buried at the end.

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?

All six parameters are optional and fully schema-documented, and with no output schema the description usefully enumerates the return fields and units. The remaining gap is edge-case behavior, such as empty results beyond the covered states or rounding/precision of the SWE percentage.

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 every parameter including defaults (count=3, max_miles=60) and the station-vs-location override is already documented in structured data. The description reinforces the count/max_miles interaction by noting that each returned station carries its distance and elevation, but adds no syntax or format detail the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names the exact resource (current snow depth at nearest SNOTEL stations) plus every derived value returned: SWE, percent of 30-year median, and 24-hour/7-day change. The word "current" plus the returned-metrics list clearly separates it from a historical snow-depth tool without needing to name it.

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?

Spells out the three accepted locators (place/ZIP, lat-lon, named station) and states that a station argument overrides location. It also bounds applicability by listing the covered states, which implicitly tells the agent when not to call it. It stops short of naming alternatives such as the history or station-listing siblings.

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.