SnowSure — Snow & Ski

Find lodging & booking link

book_lodging

Idempotent

Lodging near a resort via LUXSKI for the signed-in user. With a specific hotelName + checkIn + checkOut it PREBOOKS a live rate and returns a LUXSKI checkout URL to complete payment (we hold the rate + attribute the booking; we never charge). Without those it returns availability + a booking link. Requires a SnowSure user access token (OAuth). Payment always completes on LUXSKI.

Input Schema

TableJSON Schema

Name	Required	Description
`slug`	No	Resort slug or name, e.g. "portillo" or "Portillo". Required unless `resort` is given.
`guests`	No	Number of adults, optional
`resort`	No	Same as `slug`: the resort slug or name. Pass either one.
`checkIn`	No	Check-in date (YYYY-MM-DD)
`checkOut`	No	Check-out date (YYYY-MM-DD)
`hotelName`	No	Specific hotel to prebook (from find_powder_trips / search). With dates → returns a checkout URL.
`powderEventId`	No	Optional powder-event id to attribute the booking to

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).

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 16, 2026

addedInput schema / properties / resort

Added value: +{
+  "description": "Same as `slug`: the resort slug or name. Pass either one.",
+  "type": "string"
+}

changedInput schema / properties / slug / description

Previous value: -"Resort slug to find lodging near, e.g. verbier"New value: +"Resort slug or name, e.g. \"portillo\" or \"Portillo\". Required unless `resort` is given."

removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```

Changed2 schema fields changedJul 2, 2026

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"
-]
```

Changed4 schema fields changedJun 30, 2026

changedInput schema / properties / checkIn / description

Previous value: -"Check-in date (YYYY-MM-DD), optional"New value: +"Check-in date (YYYY-MM-DD)"

changedInput schema / properties / checkOut / description

Previous value: -"Check-out date (YYYY-MM-DD), optional"New value: +"Check-out date (YYYY-MM-DD)"

addedInput schema / properties / hotelName

Added value: +{
+  "description": "Specific hotel to prebook (from find_powder_trips / search). With dates → returns a checkout URL.",
+  "type": "string"
+}

addedInput schema / properties / powderEventId

Added value: +{
+  "description": "Optional powder-event id to attribute the booking to",
+  "type": "string"
+}

AddedJun 25, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds significant behavioral context beyond the annotations: it discloses that the tool never charges, that payment completes externally on LUXSKI, that it holds the rate, and that it attributes the booking. It also clarifies the OAuth requirement and the prebooking side effect. These details meaningfully inform an agent about what actually happens when the tool is invoked.

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 compact, front-loaded with the core purpose, and every sentence adds necessary information. It explains both modes, the OAuth requirement, and the external payment flow without repetition or filler.

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?

For a 7-parameter tool with high schema coverage and an output schema, the description is complete enough for correct invocation. It covers the essential mode switch, the user-auth prerequisite, and the external-payment side effect. Nothing critical is missing for an agent to decide when and how to call this 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?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining how combinations of parameters change behavior: hotelName + checkIn + checkOut triggers prebooking, while omitting them yields availability. This conditional semantics is not fully captured by the individual parameter descriptions and helps an agent assemble valid calls.

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 identifies the tool's purpose: it returns lodging availability and a booking link, or prebooks a live rate for a specific hotel and returns a LUXSKI checkout URL. It uses action-oriented language ('PREBOOKS', 'returns') and differentiates itself from the many read-only sibling tools by framing this as a user-specific booking action via LUXSKI.

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 states the two operating modes: with hotelName + checkIn + checkOut it prebooks, without those it returns availability and a booking link. It also specifies a prerequisite (SnowSure OAuth token). It does not name alternative sibling tools, but the conditional logic itself gives clear guidance on when to call this tool and what inputs trigger each behavior.

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

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

Need Help?