Skip to main content
Glama

Avalanche Forecast and Danger Rating MCP

Avalanche forecast

avalanche_forecast
Read-onlyIdempotent

The current avalanche forecast for a mountain place ("Alta, UT", "Snoqualmie Pass", "Mount Hood"), a forecast zone name ("Tetons", "Salt Lake") or latitude and longitude: the danger rating (1 Low to 5 Extreme) and travel advice, danger above, near and below treeline for today and tomorrow when the center issues them, avalanche problems (type, likelihood, size, aspects and elevations), the bottom line or early-season summary, issue and expiry times, and the full forecast link. Covers every zone on avalanche.org (AK, AZ, CA, CO, ID, MT, NH, NM, NY, OR, UT, WA, 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": "avalanche_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneNoA forecast zone name instead of a place, for example "Stevens Pass", "Tetons" or "Bridger Range".
placeNoA mountain town, pass, peak or "lat,lon", for example "Alta, UT" or "Girdwood, AK".
centerNoLimit zone and place matching to one center id, for example NWAC, UAC, CAIC, SAC, GNFAC.
latitudeNoLatitude, with longitude, instead of a place.
longitudeNoLongitude, with latitude.
include_discussionNoAlso return the forecaster's hazard discussion (plain text, up to 3,000 characters).

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 readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value beyond that: it names the upstream data source (avalanche.org), lists the covered states, enumerates the returned sections, and discloses the important caveat that tomorrow's treeline ratings and other fields appear only 'when the center issues them'. It does not mention rate limits or failure behavior for unmatched places.

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?

Two sentences, purpose front-loaded, then a well-organized enumeration of returned fields and coverage. Dense but readable; the repeated input-format examples ("Alta, UT", "Snoqualmie Pass", "Mount Hood") partly duplicate the schema's own parameter examples and could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of explaining return values, and it does so thoroughly: rating scale, travel advice, per-treeline elevations for two days, avalanche problem components, summary text, timestamps, and link. Combined with the annotations covering the safety profile, an agent has everything needed to call and interpret this tool.

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 each of the six parameters is already documented with examples in the schema itself. The description reinforces the place/zone/lat-lon input forms with examples like "Alta, UT" and "Tetons", but adds no meaning for center, include_discussion (e.g. its 3,000-character cap), or how place and zone interact if both are supplied. Baseline 3 is appropriate.

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?

Names the specific resource (current avalanche forecast) and enumerates what it contains: danger rating 1-5, travel advice, treeline danger, avalanche problems, bottom line, issue/expiry, and link. It also states the geographic coverage (every zone on avalanche.org across 13 states). It does not explicitly contrast itself with the siblings avalanche_centers or avalanche_danger_map, so an agent must infer that this is the full-forecast tool rather than the lookup/map tools.

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: the description explains that a place, a zone name, or lat/lon may be supplied, which tells the agent what inputs are valid, but it never says when to prefer this tool over avalanche_danger_map or avalanche_centers. No exclusions, no prerequisites, no guidance on choosing between the alternative locator forms beyond what the schema already documents.

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.