Skip to main content
Glama

SnowSure — Snow & Ski

by ai.snowsure
OverviewDiscussionsAdmin

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) shows only hotels handpicked into that tier; SnowSure shows Lux and Hip stays only. Each hotel carries an attribution-tagged booking link; booking completes on LUXSKI.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
passNoOnly resorts on this multi-resort pass, by SnowSure pass id: ikon-pass, epic-pass, indy-pass, mountain-collective, …
vibeNoOnly show handpicked hotels in this tier: lux or hip
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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / vibe / description
      Previous value: -"Only show handpicked hotels in this tier: lux, hip, family, or budget"New value: +"Only show handpicked hotels in this tier: lux or hip"
    • changedInput schema / properties / vibe / enum
      Previous value: -[
-  "lux",
-  "hip",
-  "family",
-  "budget"
-]New value: +[
+  "lux",
+  "hip"
+]
  2. Changed1 schema field changed
    • removedInput schema / properties / kind
      Removed value: -{
-  "description": "Trip length: week (seven nights from the night before the snow) or weekend (three to four nights around it). Omit for both.",
-  "enum": [
-    "week",
-    "weekend"
-  ],
-  "type": "string"
-}
  3. Changed2 schema fields changed
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "Trip length: week (seven nights from the night before the snow) or weekend (three to four nights around it). Omit for both.",
+  "enum": [
+    "week",
+    "weekend"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / pass
      Added value: +{
+  "description": "Only resorts on this multi-resort pass, by SnowSure pass id: ikon-pass, epic-pass, indy-pass, mountain-collective, …",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / region / enum
      Previous value: -[
-  "europe",
-  "north-america",
-  "asia",
-  "oceania",
-  "south-america"
-]New value: +[
+  "europe",
+  "north-america",
+  "asia",
+  "oceania",
+  "south-america",
+  "africa"
+]
  5. Changed2 schema fields changed
    • changedOutput schema / properties / markdown / description
      Previous value: -"Human-readable markdown summary of the tool result."New value: +"Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose)."
    • removedOutput schema / required
      Removed value: -[
-  "markdown"
-]
  6. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that each hotel carries a booking link and that booking completes on LUXSKI, clarifying that the tool itself does not perform bookings but returns links. No contradiction 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 moderately concise, containing marketing-like phrasing and a few redundant elements (e.g., 'bookable' and 'booking links'). However, it is well-structured with clear examples and filter explanations, and it avoids unnecessary detail.

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?

The description fully captures the tool's core functionality, expected output (ranked resorts with hotels and links), and relevant context (14-day forecast, booking completion on LUXSKI). It is sufficient for an agent to understand when and how to use the tool without missing critical information.

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?

The schema descriptions already cover all parameters (100% coverage), but the description adds clarity about the default behavior of the vibe filter (showing both Lux and Hip when no filter is applied) and provides context on how limit and region affect results. This goes beyond the schema but not extensively.

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 forecast and returns handpicked hotels with booking links, distinguishing it from siblings like find_best_powder or book_lodging. It includes a specific purpose: 'where to go AND where to stay' for powder trips.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists example queries and the intended use case: 'Use for "where should I book for powder"...' It provides guidance on optional filters (vibe, limit, region) and implies when this tool is appropriate compared to alternatives.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources