SnowSure — Snow & Ski

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

TableJSON Schema

Name	Required	Description
`limit`	No	Number of results (default: 10)
`region`	No	Filter by region
`minSnowfall`	No	Minimum 24h snowfall in cm to include (default: 5)

Output Schema

TableJSON 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 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.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, establishing a safe read operation. The description adds behavioral value by stating results are sorted by 24-hour snowfall and are current ('right now'), which are not captured in the annotations.

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 two sentences with no wasted words. The primary purpose is front-loaded, followed by the sorting behavior and two concrete use-case queries.

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 simple read-only list tool with full schema coverage, an output schema, and safety annotations, the description covers the essential purpose, usage context, and sort behavior. No critical information is missing for an agent to decide whether and how to call it.

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%, and each parameter has its own description. The tool description does not add extra meaning to the parameters beyond what the schema already provides, so the baseline of 3 applies.

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 clearly states 'Find resorts with the freshest powder snow right now' and specifies the output is 'sorted by 24-hour snowfall.' This goes beyond a generic 'find resorts' and differentiates it from sibling tools like find_resorts_by_criteria or get_snow_report by focusing on real-time freshness and a specific sort order.

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 explicitly says to use for "where is it snowing?" or "fresh powder" queries, giving clear context. However, it does not mention when not to use it or name alternative sibling tools, so it stops short of a 5.

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?