SnowSure — Snow & Ski

Powder Reels storm timelapses

get_powder_reels

Read-onlyIdempotent

Powder Reels — SnowSure archived storm timelapses with verified accumulation data burned into the frames ("Proof of Powder"). Use for "how much did it snow at X last night", "show me the storm at Alta", "biggest powder days this season", or any request for storm footage / timelapse / receipts. Returns reels newest-first with watch links.

Input Schema

TableJSON Schema

Name	Required	Description
`date`	No	Optional storm date (YYYY-MM-DD) — requires resort
`limit`	No	Number of reels to return (default: 5, max: 20)
`resort`	No	Optional resort slug to filter (e.g. "alta", "portillo")

Output Schema

TableJSON Schema

Name	Required	Description	Default
`markdown`	No	Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating a safe read operation. The description adds behavioral context beyond annotations: it mentions that accumulation data is burned into frames ('Proof of Powder'), that results are returned newest-first, and that watch links are provided. No contradictions with annotations.

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?

The description is a single paragraph that front-loads the tool's core purpose, then lists example queries, and ends with the return behavior. It is efficient but could be slightly more structured with bullet points. Every sentence adds value.

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?

Given that an output schema exists (not shown but acknowledged), the description does not need to explain return values. It covers filtering options (resort, date), ordering, the nature of the data (verified accumulation), and typical use cases. This is sufficient for an agent to select and invoke the tool correctly.

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% with all three parameters (date, limit, resort) having descriptions. The description does not add significant new semantics beyond the schema; it restates that resort is optional and date requires resort (already in schema). The use-case examples indirectly guide parameter usage but do not provide deeper meaning. Baseline 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves Powder Reels — archived storm timelapses with verified accumulation data. It provides specific example queries like 'how much did it snow at X last night' and mentions the output ordering (newest-first with watch links). This distinguishes it from sibling tools focused on forecasts, webcams, or snow reports.

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?

The description explicitly lists use cases for storm footage, timelapses, and powder receipts. While it does not explicitly state when not to use this tool, the context makes it clear it is for historical, verified storm recaps rather than live conditions or forecasts. The sibling tools like get_webcam_status and get_snow_report provide alternatives, but the description does not directly call them out.

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

All SnowSure — Snow & Ski tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation2/5

Multiple tool clusters have unclear boundaries: get_resort overlaps with get_resort_info and get_resort_photos, ask_snowdata competes with compare_resorts and the El Niño tools, and get_snow_history / get_season_leaderboard / get_insights cover similar retrospective ground. The descriptions try hard to route agents, but with 45 tools an agent will frequently have to choose between near-equivalent options.

Naming Consistency4/5

Most tools follow a clear verb_noun snake_case pattern: get_resort_info, compare_resorts, find_best_powder, book_lodging, save_resort. Minor deviations like ask_snowdata and the very similar get_resort vs get_resort_info names prevent a 5, but overall the naming convention is predictable.

Tool Count2/5

45 tools is well above the 25+ threshold and puts a heavy selection burden on the agent. While the domain is broad, many tools are narrow variations on conditions, history, road data, or trip planning that could be consolidated or exposed as configurable parameters.

Completeness4/5

The toolkit covers an impressively wide lifecycle: resort discovery, photos, live conditions, forecasts, history, comparisons, passes, flights, lodging, road status, alerts, and user saved resorts. Minor gaps exist such as no lift-ticket booking, no lesson/rental booking, and flight search only produces links rather than a booking flow, but agents can generally complete core snow-trip workflows.

Resources

Need Help?