Skip to main content
Glama

Avalanche Forecast and Danger Rating MCP

Avalanche centers

avalanche_centers
Read-onlyIdempotent

US avalanche centers (all, or in one state) with their forecast zones, website, time zone and season status: issuing danger ratings, in season without a rating today, or off season, plus the highest current danger.

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

Input Schema

NameRequiredDescriptionDefault
stateNoUS state, 2-letter code or name, for example WA, UT or Colorado.

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, idempotent, non-destructive, open-world behavior, so the description's job is value-add — and it delivers by disclosing the three-way season status classification (issuing ratings / in season without a rating today / off season) and that a 'highest current danger' value is included. It does not mention the upstream data source, freshness, or staleness of the rating, which is the one behavioral gap.

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 front-loaded sentence with no filler; the scope ('all, or in one state') appears before the returned-field list, which is the right ordering. The colon-separated season-status clause is dense but each element 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?

No output schema exists, so the description must carry return-value information — and it does, enumerating every field category including the computed 'highest current danger'. For a single optional-parameter read tool this is close to sufficient; only the shape/typing of the danger value and any data-freshness caveat are absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and already explains the 2-letter code or full name for 'state'. The description adds meaning beyond the schema by making explicit that omitting the filter returns all centers as well as the in-state subset, which the schema's optional parameter does not spell out.

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 a specific resource (US avalanche centers) and enumerates the attributes returned (forecast zones, website, time zone, season status, highest current danger). It never contrasts itself with avalanche_danger_map or avalanche_forecast, but an agent can still tell it is the discovery/metadata listing.

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?

The parenthetical '(all, or in one state)' implies the two usage modes, and the season-status taxonomy hints at why you'd call it (to find which centers are actively rating). There is no explicit when-to-use versus the sibling forecast/map tools and no stated prerequisites or exclusions.

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.