Skip to main content
Glama

SnowSure — Snow & Ski

by ai.snowsure
OverviewDiscussionsAdmin

Find fresh powder

find_best_powder
Read-onlyIdempotent

Find resorts with the freshest powder snow right now. Returns resorts sorted by 24-hour snowfall. Use for "where is it snowing?" or "fresh powder" queries.

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of results (default: 10)
regionNoFilter by region
minSnowfallNoMinimum 24h snowfall in cm to include (default: 5)

Output 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
    • 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"
+  ]
+}
  2. 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."
  3. 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."
  4. 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"
+}
  5. 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"
+]
  6. 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"
+]
  7. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world safety, so the description isn't burdened with that. It does add two useful facts beyond annotations: results are ordered by 24-hour snowfall, and the data reflects current/near-real-time conditions ('right now'). It says nothing about result volume or how the default snowfall threshold shapes the set, so it is additive but thin.

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?

Three short sentences, each doing distinct work: purpose, return ordering, and query-intent triggers. The core capability is front-loaded with zero filler.

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?

For a zero-required-parameter read tool with full schema coverage, complete annotations, and an output schema, the description covers what to expect and when to reach for it. The only omission is sibling disambiguation among the many resort-discovery tools.

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%, so limit, region, and minSnowfall are fully documented in the schema, including defaults and the region enum. The description's mention of '24-hour snowfall' aligns with minSnowfall but adds no syntax, units, or interaction guidance beyond what the schema already provides — baseline 3.

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 ('Find resorts') plus the ranking criterion ('freshest powder snow right now', 'sorted by 24-hour snowfall'), which lets an agent distinguish it from generic list tools. However, it never contrasts itself with similar siblings like get_snow_report, search_resorts, or find_resorts_by_criteria, so the boundary is inferred rather than stated.

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 user-intent triggers ('where is it snowing?' / 'fresh powder' queries), which is exactly the phrasing an agent matches against. It stops short of explicit exclusions or naming the alternative tool for non-powder resort lookups, so it is clear context without routing rules.

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