Skip to main content
Glama

SnowSure — Snow & Ski

by ai.snowsure
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order: snowsure (AI rating), forecast (14-day snow), recent (24h snowfall), depth (current base)
limitNoNumber of resorts to return (default: 10, max: 50)
regionNoFilter by region

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
resortsYes
markdownYesHuman-readable markdown summary (required for ChatGPT Instant mode).
subtitleNo
updatedAtYesOldest data time among the listed resorts (ISO-8601); null when none carries one. Never request time.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
  2. Changed3 schema fields changed
    • 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."
  3. Changed2 schema fields changed
    • addedOutput schema / properties / resorts / items / properties / forecast7dCm
      Added value: +{
+  "type": "number"
+}
    • addedOutput schema / properties / resorts / items / properties / forecastHorizonDays
      Added value: +{
+  "type": "number"
+}
  4. Changed2 schema fields changed
    • 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"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / region / enum
      Previous value: -[
-  "europe",
-  "north-america",
-  "asia",
-  "oceania",
-  "south-america"
-]New value: +[
+  "europe",
+  "north-america",
+  "asia",
+  "oceania",
+  "south-america",
+  "africa"
+]
  6. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses a real behavioral quirk: forecast14dCm is only present for entitled callers (SnowSure Pro or a signed-in reader's saved resort), and it instructs the agent to read forecastHorizonDays before naming a total. That conditional-field/entitlement disclosure is exactly the kind of context annotations cannot carry.

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 trigger phrases are front-loaded in the first two sentences, and the longer third sentence on forecast-field availability earns its length by preventing a likely misstatement. Slightly dense but no padding.

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?

An output schema exists so return values need not be explained, yet the description still covers the two fields whose presence varies by entitlement. With 100% schema coverage, zero required params, and annotations present, nothing an agent needs to call this correctly is missing.

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 the baseline is 3, but the description adds meaning beyond the schema: it links the sort values to what the rows actually contain and explains the entitlement-dependent presence of forecast14dCm, which the schema does not convey.

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?

Specific verb+resource (global snow report of top-ranked resorts) plus a stated ordering mechanism (SnowSure score, forecast, or recent snowfall). It is clearly distinguishable from siblings like get_regional_summary, get_my_snow_report, and get_season_leaderboard, which are scoped differently.

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?

It gives concrete trigger phrases ('where has the best snow?', 'top ski resorts right now') which tell the agent when this tool fits. It stops short of naming an alternative or an exclusion (e.g. when to prefer find_best_powder or get_regional_summary instead), so it is clear context without routing.

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 toolsInspect
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