SnowSure — Snow & Ski

Global snow report

get_snow_report

Read-onlyIdempotent

Get the global snow report with top-ranked resorts by snow conditions. Returns resorts sorted by SnowSure score, forecast, or recent snowfall. Use this for "where has the best snow?" or "top ski resorts right now" queries. Each row carries forecast7dCm and forecastHorizonDays; forecast14dCm is present only for a caller entitled to the fortnight (SnowSure Pro, or a resort in a signed-in reader's My Mountains), so read forecastHorizonDays before naming a forecast total. Each row also carries forecast7dBands: the free seven days at base, mid and summit, each with the elevation its run was made at — rain at the base can be snow at the summit, so quote the height with the figure.

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": "get_snow_report"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort order: snowsure (AI rating), forecast (forecast snow at the caller's horizon: 7 days, or 14 when entitled; the list's metricKey is forecast7d or forecast14d to match and metricWindowDays states the days), recent (24h snowfall), depth (current base)
`limit`	No	Number of resorts to return (default: 10, max: 50)
`region`	No	Filter by region

Output Schema

Name	Required	Description
`title`	Yes
`resorts`	Yes
`markdown`	Yes	Human-readable markdown summary (required for ChatGPT Instant mode).
`subtitle`	No
`updatedAt`	Yes	Oldest data time among the listed resorts (ISO-8601); null when none carries one. Never request time.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

addedOutput schema / properties / resorts / items / properties / forecast7dBands

Added value: +{
+  "description": "The free seven days at each reporting height (SS-W-2343): base, mid and summit, each { band, elevationM, elevationFt, total7dCm } or null when that band has no run. The height is the one the run was made at; quote it beside the figure. Not gated. Null when the row carries no band.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

addedOutput schema / properties / resorts / items / properties / forecastPoint

Added value: +{
+  "description": "The height forecast7dCm / forecast14dCm were made at (SS-W-2268): { band, elevationM, elevationFt }, band being the headline reporting height (mid or summit). Quote it beside the total. Absent when the row knows no height.",
+  "type": [
+    "object",
+    "null"
+  ]
+}

Changed1 schema field changedOct 22, 2026

changedInput schema / properties / sort / description

Previous value: -"Sort order: snowsure (AI rating), forecast (14-day snow), recent (24h snowfall), depth (current base)"New value: +"Sort order: snowsure (AI rating), forecast (forecast snow at the caller's horizon: 7 days, or 14 when entitled; the list's metricKey is forecast7d or forecast14d to match and metricWindowDays states the days), recent (24h snowfall), depth (current base)"

Changed2 schema fields changedOct 10, 2026

changedOutput schema / properties / resorts / items / properties / forecast14dCm / description

Previous value: -"SnowSure blended forecast total (cm) over the forward 14 days. Present only when forecastHorizonDays is 14 — a caller entitled to the fortnight (SnowSure Pro, or a signed-in reader on a favourite resort). Absent or null for an anonymous or free caller: read forecast7dCm instead, and never label it a 14-day total."New value: +"SnowSure blended forecast total (cm) over the forward 14 days. Present only when forecastHorizonDays is 14 — a caller entitled to the fortnight (SnowSure Pro, or a signed-in reader on a resort in their My Mountains). Absent or null for an anonymous or free caller: read forecast7dCm instead, and never label it a 14-day total."

changedOutput schema / properties / resorts / items / properties / forecastHorizonDays / description

Previous value: -"The forecast horizon this caller is entitled to: 14 with SnowSure Pro or on a signed-in reader’s favourite, 7 otherwise. Read it before naming any forecast total."New value: +"The forecast horizon this caller is entitled to: 14 with SnowSure Pro or on a resort in a signed-in reader’s My Mountains, 7 otherwise. Read it before naming any forecast total."

Changed3 schema fields changedOct 10, 2026

addedOutput schema / properties / resorts / items / properties / forecast14dCm / description

Added value: +"SnowSure blended forecast total (cm) over the forward 14 days. Present only when forecastHorizonDays is 14 — a caller entitled to the fortnight (SnowSure Pro, or a signed-in reader on a favourite resort). Absent or null for an anonymous or free caller: read forecast7dCm instead, and never label it a 14-day total."

addedOutput schema / properties / resorts / items / properties / forecast7dCm / description

Added value: +"SnowSure blended forecast total (cm) over the forward seven days, from the resort’s local today. The free window, served to every caller."

addedOutput schema / properties / resorts / items / properties / forecastHorizonDays / description

Added value: +"The forecast horizon this caller is entitled to: 14 with SnowSure Pro or on a signed-in reader’s favourite, 7 otherwise. Read it before naming any forecast total."

Changed2 schema fields changedSep 22, 2026
- addedOutput schema / properties / resorts / items / properties / forecast7dCm
```
Added value: +{
+  "type": "number"
+}
```
- addedOutput schema / properties / resorts / items / properties / forecastHorizonDays
```
Added value: +{
+  "type": "number"
+}
```

Changed2 schema fields changedSep 15, 2026

addedOutput schema / properties / updatedAt / description

Added value: +"Oldest data time among the listed resorts (ISO-8601); null when none carries one. Never request time."

changedOutput schema / properties / updatedAt / type

Previous value: -"string"New value: +[
+  "string",
+  "null"
+]

Changed1 schema field changedJul 3, 2026

changedInput schema / properties / region / enum

Previous value: -[
-  "europe",
-  "north-america",
-  "asia",
-  "oceania",
-  "south-america"
-]New value: +[
+  "europe",
+  "north-america",
+  "asia",
+  "oceania",
+  "south-america",
+  "africa"
+]

First observedJun 19, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive); the description adds the truly load-bearing behavior: entitlement gating on forecast14dCm, the need to read forecastHorizonDays before quoting a total, and the elevation-band caveat that base rain can be summit snow. These are exactly the nuances an agent would otherwise get wrong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and intended queries are front-loaded, with caveats trailing in a logical order. It is somewhat dense in the forecast/band explanations, but each sentence carries actionable information rather than 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 list tool with an output schema, the description still supplies the entitlement and elevation-band interpretation rules that an output schema alone would not convey. Nothing an agent needs to answer a 'best snow now' question correctly 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 coverage is 100%, so the enum meanings (including depth) are already fully documented in the schema; the description's 'sorted by SnowSure score, forecast, or recent snowfall' even omits the depth option. With the schema doing the heavy lifting, baseline 3 applies.

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 and resource ('Get the global snow report with top-ranked resorts by snow conditions') plus the return ordering. It implicitly distinguishes itself from the personal sibling get_my_snow_report via 'global', but never names that sibling explicitly, so it falls just short of a 5.

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?

Gives concrete query intents it serves ('where has the best snow?', 'top ski resorts right now'), which usefully routes the agent away from history/forecast-only siblings. It stops short of stating when NOT to use it or naming a specific alternative tool.

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?