SnowSure

Overview Schema Source Related Servers Discussions Admin

Global snow report

get_snow_report

Read-onlyIdempotent

Retrieve global snow report with top-ranked resorts by snow conditions. Sort by AI score, forecast, recent snowfall, or depth. Filter by region.

Instructions

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.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Sort order: snowsure (AI rating), forecast (14-day snow), recent (24h snowfall), depth (current base)
`limit`	No	Number of resorts to return (default: 10, max: 50)
`region`	No	Filter by region

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and idempotentHint, indicating safe read behavior. The description adds no new behavioral context beyond what annotations provide, which is adequate but not enhanced.

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 filler, front-loaded with the core purpose, and efficiently conveys use cases.

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?

Given the existence of a full output schema, the description doesn't need to explain return values. It covers the tool's primary function and query intent, but omits mention of region filtering and limit, which are in the schema. Still, the context is sufficient for most agents.

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 description need not repeat all parameter details. However, the description mentions only three sort options (snowsure, forecast, recent) while the schema includes 'depth', and it does not explain 'limit' or 'region' parameters, providing partial but incomplete semantics.

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?

The description clearly states the tool returns a global snow report with top-ranked resorts by snow conditions, providing specific use cases. However, it does not differentiate from similar sibling tools like 'get_my_snow_report' or 'find_best_powder'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit example queries for when to use the tool, but lacks guidance on when not to use it or mention of alternatives among the many sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.