SnowSure — Snow & Ski

List saved resorts

list_saved_resorts

Read-onlyIdempotent

List the signed-in user's saved resorts. Requires a SnowSure user access token (OAuth); without one it returns an authorization-required error telling the agent how to connect.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

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.5/5.0

Behavior4/5

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

The description adds behavioral insight beyond annotations by mentioning the OAuth requirement and the authorization error behavior, which annotations alone do not cover.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences: the first states the purpose, the second adds critical auth context. No wasted words, and the most important information is front-loaded.

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?

With no parameters and an output schema available, the description covers the purpose, auth requirement, and error handling, which is complete for a simple list tool.

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?

There are no parameters, so schema coverage is 100%. The description does not need to add parameter details; the context about auth is extra and not parameter-related. Baseline 4 for zero parameters.

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 'List the signed-in user's saved resorts' with a specific verb and resource, and it distinguishes from sibling tools like save_resort and remove_saved_resort.

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 specifies the requirement for a SnowSure user access token and explains the error response when missing, providing clear context for when to use the tool.

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.

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?