SnowSure — Snow & Ski

Southern Hemisphere report

get_southern_hemisphere_report

Read-onlyIdempotent

Get snow conditions for Southern Hemisphere ski resorts (Australia, New Zealand, Argentina, Chile) currently in season. Answers "is Perisher / Portillo / Valle Nevado open right now and what are the current conditions", "is the Australian ski season underway", and "which Southern Hemisphere region — the Andes, Australia, or NZ — has the best snow right now". Use for June–October SH ski queries. Prefers operator-verified data when available. Do NOT use for a specific opening DATE — use get_season_openings instead. Note that the SH is not the only place to ski in the northern summer: a handful of NH glaciers run summer or year-round operations (Zermatt/Matterhorn Ski Paradise skis all year; Passo dello Stelvio, Stryn and Galdhøpiggen run deep into autumn; Hintertux, Saas-Fee, Tignes, Les Deux Alpes and Timberline have dated summer windows that close). For those, call get_resort on the named glacier — summer windows are tracked per resort and a glacier being famous for summer skiing does not mean it is open today.

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_southern_hemisphere_report"
  }
}

Input Schema

Name	Required	Description
`sort`	No	Sort: snowsure (AI score), recent (24h snow), depth (base depth)
`limit`	No	Max resorts (default: 10)
`country`	No	Optional country filter

Output Schema

Name	Required	Description	Default
`markdown`	No	Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJul 2, 2026

changedOutput schema / properties / markdown / description

Previous value: -"Human-readable markdown summary of the tool result."New value: +"Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose)."

removedOutput schema / required
```
Removed value: -[
-  "markdown"
-]
```

First observedJun 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is well-covered. The description adds value by stating the tool 'Prefers operator-verified data when available,' which is a useful behavioral trait not captured in annotations. The description is fully consistent with annotations.

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?

The description is front-loaded with the core purpose and example queries, then branches into usage guidelines and exclusions. Every sentence earns its place, but the description is somewhat long (6 sentences) and could be tightened slightly. The structure is logical and clear.

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?

Given the tool has 3 optional parameters, 100% schema coverage, an output schema, and rich annotations, the description is complete. It covers geographic scope, seasonal context, example queries, alternatives, and even edge cases about NH summer glaciers. No gaps remain for an agent to use this tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds value beyond the schema by providing context for the 'sort' parameter (AI score, 24h snow, base depth) and explaining the default limit. It does not, however, detail the output schema or explain how the country filter interacts with the tool's geographic scope.

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 uses a specific verb ('Get') with a clear resource ('snow conditions for Southern Hemisphere ski resorts') and explicitly lists the countries (Australia, New Zealand, Argentina, Chile). It distinguishes itself from the 43 sibling tools by providing concrete example queries and noting when to use get_season_openings instead.

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

Usage Guidelines5/5

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

The description provides explicit usage guidance: use for June–October SH ski queries, provides a specific sibling tool to not use (get_season_openings for opening dates), and even details when to use get_resort for NH glacier summer operations. This is exemplary coverage of when, when-not, and alternatives.

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?