SnowSure — Snow & Ski

Search resorts

search_resorts

Read-onlyIdempotent

Search for ski resorts by name, country, region, or US state / Canadian province (name or code, e.g. "Idaho", "ID", "BC"). Returns matching resorts with basic conditions. Use for "find resorts in [location]" or "search [name]" queries.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_resorts"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return (default: 20)
`query`	No	Search query - can be resort name, country, or partial match
`country`	No	Filter by exact country name (e.g., "Japan", "Switzerland", "United States")

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

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

First observedJun 19, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so the safety profile is covered. The description adds that results include "basic conditions" and that name/state codes are matched, but says nothing about limits, ranking, or empty-result behavior beyond the schema default.

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?

Two tight sentences: searchable fields first, return content second, example queries last. Nothing is redundant with the schema or title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, full parameter documentation, and annotations all present, the description only needs to frame intent and search dimensions, which it does. The remaining gap is disambiguation from the many sibling resort tools, which it never addresses.

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 baseline is 3; the description earns above baseline by clarifying that state/province can be given as either name or code with concrete examples ("Idaho", "ID", "BC"), which the schema's query and country fields do not convey. It still leaves the interaction between query and country unstated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (search) and resource (ski resorts) plus the searchable dimensions: name, country, region, US state / Canadian province. An agent can tell this is a location-oriented lookup, though it never distinguishes itself from the close sibling find_resorts_by_criteria or get_resort.

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

Usage Guidelines3/5

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

Provides example query phrasings ("find resorts in [location]", "search [name]"), which implies usage, but gives no when-not guidance and does not route the agent to alternatives like find_resorts_by_criteria or get_resort for single-resort lookups.

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?