SnowSure — Snow & Ski

Compare resorts

compare_resorts

Read-onlyIdempotent

Compare 2–4 resorts side by side across snow, terrain, and live conditions — every value comes from the SnowSure conditions resolver/contract. Use for head-to-head stat questions phrased as either/or: "which gets more average annual snowfall, X or Y", "which has the greater vertical drop / higher base or summit elevation / bigger skiable area, X or Y", "which typically opens earlier, X or Y". Optionally restrict to specific dimensions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slugs": "<slugs>"
    },
    "name": "compare_resorts"
  }
}

Input Schema

Name	Required	Description	Default
`slugs`	Yes	2–4 resort slugs to compare, e.g. ["verbier","val-disere"]
`dimensions`	No	Optional subset of: score, status, depth, snowfall24h, forecast14d, lifts, runs, snowQuality, base, summit, terrainBeginner, terrainIntermediate, terrainAdvanced, vertical, longestRun

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.

Changed1 schema field changedAug 26, 2026

changedInput schema / properties / dimensions / description

Previous value: -"Optional subset of: score, status, depth, snowfall24h, forecast14d, lifts, runs, snowQuality, summit, vertical, longestRun"New value: +"Optional subset of: score, status, depth, snowfall24h, forecast14d, lifts, runs, snowQuality, base, summit, terrainBeginner, terrainIntermediate, terrainAdvanced, vertical, longestRun"

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

AddedJun 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so safety is established. The description adds behavioral context by sourcing values from the 'SnowSure conditions resolver/contract' and noting 'live conditions', which implies data freshness. This goes beyond annotations without contradicting them.

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 three sentences with zero filler: it fronts the core purpose, then usage context, then the optional restriction. Every sentence contributes unique value, and the structure is scannable for an agent.

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 output schema exists (so return format is documented elsewhere), annotations cover safety, and the schema fully explains both parameters, the description is complete for proper tool invocation. It covers what the tool does, when to use it, and data provenance—nothing needed for correct usage 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?

Schema description coverage is 100% — both `slugs` and `dimensions` are fully described in the schema (including an example for slugs and an explicit list of dimension values). The description adds little beyond restating the optional restriction, so it does not materially enhance parameter understanding beyond the schema.

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 states a specific verb ('Compare'), a specific resource ('resorts'), and a precise scope ('2–4 resorts side by side across snow, terrain, and live conditions'). It also provides concrete example queries that clarify intent, and clearly distinguishes itself from sibling tools like compare_forecasts and compare_passes by focusing on resort attributes.

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 frames when to use the tool: 'Use for head-to-head stat questions phrased as either/or' with multiple examples. It does not name alternatives or exclusions (e.g., when to use compare_passes instead), but the provided context is clear enough that an agent can infer applicability from the examples and sibling names.

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?