Skip to main content
Glama
avalanche-forecast-danger-rating-mcp

avalanche-forecast-danger-rating-mcp

Avalanche danger map

avalanche_danger_map
Read-onlyIdempotent

Retrieve current US avalanche danger ratings by forecast zone, state, or center, filtered by danger level and sorted highest first, with validity windows and warnings.

Instructions

Current avalanche danger for every US avalanche forecast zone (about 90 zones from about 30 centers), or one state or center, sorted highest first, with counts by danger level, off-season zones, the validity window of each rating and avalanche warnings.

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

Input Schema

NameRequiredDescriptionDefault
stateNoUS state, 2-letter code or name, for example WA, UT or Colorado.
centerNoOne avalanche center id, for example NWAC, UAC, CAIC, SNFAC.
min_levelNoOnly zones at or above this danger level, 1 Low to 5 Extreme.
rated_onlyNoOnly zones that have a danger rating right now.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds real behavioral context beyond that: results are sorted highest danger first, include per-level counts, flag off-season zones, carry each rating's validity window, and surface avalanche warnings — details an agent cannot get from the annotations or schema.

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?

A single dense sentence, front-loaded with the primary payload ('Current avalanche danger for every US avalanche forecast zone') and then the qualifiers and return contents. Nothing is redundant, though the comma-chained clause list makes it slightly harder to scan than a short structured breakdown would be.

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 does so well — sorted order, per-level counts, off-season flags, validity windows, and warnings. For a read-only, open-world query tool with 0 required params, that is nearly complete; only explicit sibling differentiation is missing.

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 state, center, min_level, and rated_only are already fully documented in the input schema. The description restates the state/center filtering but adds nothing about min_level thresholds or what rated_only excludes, so it neither compensates for nor improves on the schema — baseline 3 applies.

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 specific resource and scope: current avalanche danger for all ~90 US forecast zones from ~30 centers, or narrowed to one state or center. It is unambiguous what the tool returns, but it never names or contrasts with the sibling tools avalanche_centers and avalanche_forecast, so the agent must infer that this is the aggregate map view rather than a single-forecast lookup.

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 only implied by the scope phrasing — 'every zone ... or one state or center' tells the agent it can broaden or narrow, but there is no explicit when-to-use versus when to call avalanche_forecast instead. No prerequisites, exclusions, or fallback guidance are stated.

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