SnowSure — Snow & Ski

Resort photo gallery

get_resort_photos

Read-onlyIdempotent

INTERACTIVE PHOTO GALLERY CAROUSEL — official SnowSure resort photos (hero + Sanity gallery). REQUIRED for: photos, pictures, images, gallery, "show me photos of Vail/Aspen". Never use web search or inline images — call this tool. Do NOT use get_destination, get_resort_info, or ask_snowdata for photo requests.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	No	Resort slug or name, e.g. "portillo" or "Portillo". Required unless `resort` is given.
`resort`	No	Same as `slug`: the resort slug or name. Pass either one.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`resort`	No	Structured resort payload for inline widget rendering.
`markdown`	Yes	Human-readable markdown summary (required for ChatGPT Instant mode).

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 identifier (e.g., \"aspen-mountain\", \"jackson-hole\", \"niseko-hanazono-resort\")"New value: +"Resort slug or name, e.g. \"portillo\" or \"Portillo\". Required unless `resort` is given."

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

First observedJun 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive). The description adds useful behavioral context beyond those annotations: the returned content is an interactive carousel sourced from official SnowSure hero and Sanity gallery images, and it is the designated photo-handling tool rather than a general web search.

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 and front-loaded, with every clause serving a purpose: what the tool returns, when it is mandatory, and which alternatives to avoid. There is no filler or redundant restating of the title.

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 low-complexity tool with full input schema documentation, an output schema, and strong annotations, the description supplies the missing operational context: when to route to it, what content category it covers, and which sibling tools are inappropriate. Nothing essential is missing.

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?

The input schema already documents both parameters fully, including examples and the note that either slug or resort can be passed. The description adds no new parameter-level meaning, so the baseline score of 3 is appropriate given 100% 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 names the specific resource (official SnowSure resort photos), the output (interactive photo gallery carousel), and the exact trigger requests it covers. It also distinguishes itself from sibling tools by explicitly excluding get_destination, get_resort_info, and ask_snowdata for photo requests.

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 states explicitly when this tool is required, including example user phrasings like 'show me photos of Vail/Aspen'. It also gives direct negative guidance: never use web search or inline images, and do not use alternative sibling tools for photo requests.

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?