Skip to main content
Glama

Snow Depth and Snowpack (SNOTEL) MCP

Find SNOTEL stations

snotel_stations
Read-onlyIdempotent

Search the active USDA NRCS SNOTEL stations by state, name, county, minimum elevation or distance from a place (nearest first). Returns name, triplet (for the other tools), state, county, elevation, coordinates and the NRCS station page.

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

Input Schema

NameRequiredDescriptionDefault
nameNoPart of a station name, such as "Pass" or "Summit".
limitNoMaximum stations returned. Default 20.
stateNoState code or name.
countyNoCounty name.
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_milesNoRadius around the place in miles. Default 50.
min_elevation_ftNoOnly stations at or above this elevation in feet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior. The description adds useful context beyond that: only active stations are searched, distance results are nearest first, and the returned fields are listed. It does not describe pagination or output structure, but it covers the key behavioral traits for a search tool.

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?

The description is two tightly written sentences with no wasted wording. The search scope and filters are front-loaded, followed by the return fields. Every clause earns its place.

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 nine optional parameters, full schema coverage, and safety annotations, the description supplies the missing high-level context: active-only filtering, nearest-first ordering, and returned fields. It does not specify the response container or pagination shape, which is a gap because there is no output schema, but the core information needed to call the tool is present.

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 all nine parameters are already documented with meanings and defaults. The description summarizes the filter groups and adds the nearest-first ordering for distance searches, but it does not add syntax or constraints beyond the schema. This matches the baseline for a fully documented 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 gives a specific verb and resource: search active USDA NRCS SNOTEL stations. It also states the filter dimensions and return fields, and notes the triplet is used by other tools. It does not explicitly contrast itself with the snow measurement siblings, so it falls short of full sibling differentiation.

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 by saying the triplet is 'for the other tools,' suggesting this is a station-discovery step before measurement tools. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative such as snow_depth or snowpack_by_state.

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.