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`	Yes	Resort slug identifier (e.g., "aspen-mountain", "jackson-hole", "niseko-hanazono-resort")

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

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare safe read-only behavior. The description adds useful context about the output format (interactive carousel, official SnowSure photos) but doesn't contradict annotations. No additional behavioral traits needed beyond what's provided.

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?

Extremely concise with no wasted words. Key information is front-loaded with capitalization for emphasis, and every 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?

Given the simple single-parameter tool with output schema and annotations, the description is fully complete. It covers purpose, usage, and exclusions without missing any essential context.

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?

Schema coverage is 100%, so the description adds minimal value beyond the schema's parameter definition. It provides example slugs but no extra semantic meaning.

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's purpose: retrieving interactive photo galleries for resorts, using specific verbs like 'get photos' and resources. It distinguishes from siblings by explicitly forbidding use of web search or other tools 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?

Provides explicit when-to-use and when-not-to-use guidance, listing trigger keywords (photos, pictures, images, gallery) and naming sibling tools to avoid (get_destination, get_resort_info, ask_snowdata).

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.

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

Need Help?