Skip to main content
Glama

Powder to the People Snow Reports

Resort snowfall history

get_resort_snow_history
Read-onlyIdempotent

Use this for average annual snowfall, past season totals, the snowiest season, or the best months at a resort. Accepts a resort name or slug. Modeled archive, completed seasons only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resort": "<resort>"
    },
    "name": "get_resort_snow_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
resortYesResort name or slug, e.g. 'alta' or 'Mt. Baker'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / resort / description
      Previous value: -"Resort slug, e.g. alta"New value: +"Resort name or slug, e.g. 'alta' or 'Mt. Baker'"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive, closed-world, so the description's job is to add data provenance. It does exactly that with 'Modeled archive, completed seasons only' — a material caveat that the numbers are modeled rather than measured, and that the in-progress season is absent. It does not add anything about return shape or granularity, but the added caveat is high-value.

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?

Three short sentences, front-loaded with the usage trigger and ending on the most important caveat. The middle sentence largely duplicates the schema's parameter description and could be dropped, but nothing else is wasted.

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?

For a single-parameter read tool with no output schema, the description usefully enumerates the categories of data returned, which compensates for the absent return schema. Missing only minor detail such as units or time granularity of season totals.

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?

There is only one parameter and the schema documents it at 100% coverage with an example ('alta' or 'Mt. Baker'). The description's 'Accepts a resort name or slug' restates the schema rather than adding matching, normalization, or ambiguity rules, so 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?

It enumerates what the tool returns (average annual snowfall, past season totals, snowiest season, best months) for a single resort, which makes it distinguishable from get_resort_snow (current) and get_region_snow/get_top_snowfall (aggregate) by scope. The verb is soft ('Use this for') rather than a direct 'Retrieve snowfall history', but the resource and scope are unambiguous.

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?

'Use this for average annual snowfall, past season totals...' gives concrete triggering questions, and 'completed seasons only' implicitly excludes current-season/forecast questions. It does not name a specific alternative for those excluded cases, so it stops short of full when/when-not routing.

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.

Resources