Skip to main content
Glama

SnowSure — Snow & Ski

by ai.snowsure

Find bookable powder trips

find_powder_trips
Read-onlyIdempotent

Powder trips you can BOOK: ranks resorts by their 14-day forecast (best chance of fresh snow in the bookable window) and returns handpicked luxury ski hotels at each — "where to go AND where to stay". Use for "where should I book for powder", "best powder trip this month", "book a ski trip with good snow coming". Optional vibe filter (lux | hip | family | budget) shows only hotels handpicked into that tier. Each hotel carries an attribution-tagged booking link; booking completes on LUXSKI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vibeNoOnly show handpicked hotels in this tier: lux, hip, family, or budget
limitNoNumber of destinations (default: 5)
regionNoFilter destinations by region

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
markdownNoHuman-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.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds booking flow details (links to LUXSKI) and reliance on forecast data, no contradictions.

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?

Description is moderately long but well-structured, front-loading purpose and examples. Each 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?

With output schema present, description doesn't need to detail return values. Covers purpose, parameters, usage, and external booking, making it fully adequate for the tool's complexity.

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 covers all 3 params (100% coverage). Description adds context for vibe filter ('handpicked hotels in that tier') and default limit, enhancing semantic understanding.

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 ranks resorts by 14-day powder forecast and returns handpicked luxury hotels, differentiating it from siblings like find_best_powder or plan_ski_trip by focusing on bookable trips with accommodation.

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?

Provides example queries ('where should I book for powder', 'best powder trip this month') and lists optional vibe filter. Lacks explicit when-not-to-use or alternatives, but usage context is clear.

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 toolsInspect
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