SnowSure — Snow & Ski

Resort weather forecast

get_weather_forecast

Read-onlyIdempotent

Get detailed day-by-day weather forecast for a resort including temperature, snowfall, wind, and conditions for each of the next 7 days — 14 with SnowSure Pro, or for a resort in My Mountains when signed in.

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

Input Schema

Name	Required	Description
`days`	No	Number of days to forecast (default: 7, max: 14)
`slug`	No	Resort slug or name, e.g. "portillo" or "Portillo". Required unless `resort` is given.
`resort`	No	Same as `slug`: the resort slug or name. Pass either one.

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.

Changed3 schema fields changedSep 16, 2026

addedInput schema / properties / resort

Added value: +{
+  "description": "Same as `slug`: the resort slug or name. Pass either one.",
+  "type": "string"
+}

changedInput schema / properties / slug / description

Previous value: -"Resort slug"New value: +"Resort slug or name, e.g. \"portillo\" or \"Portillo\". Required unless `resort` is given."

removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```

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

A3.5/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the description is not burdened with safety disclosure. It adds meaningful behavioral context by disclosing that the default horizon is 7 days, 14 days requires SnowSure Pro, and My Mountains resorts work when signed in. It does not cover error behavior or rate limits, keeping it from a 5.

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 definition is a single front-loaded sentence that quickly states the action and resource. It is efficient overall, though the list of included weather fields is somewhat redundant given the output schema, and the access clause at the end makes it slightly dense.

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 simple read-only forecast tool with a rich output schema and clear annotations, the description supplies the essential context: forecast horizon, included data, tier gating, and signed-in scope. It does not mention pagination or error cases, but those are minor given the schema and annotations. Overall it is complete enough to invoke correctly.

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 the schema already documents days, slug, and resort with defaults, maximums, and aliasing rules. The description reinforces the 7/14-day horizon but adds no new syntax or constraints beyond the schema. Baseline 3 is appropriate when the schema carries the parameter 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 a specific verb and resource: get a day-by-day weather forecast for a resort. It lists the forecast fields and horizon, making the tool's purpose unambiguous. However, it does not differentiate from siblings like get_snow_report or compare_forecasts, so it stops short of a 5.

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

Usage Guidelines2/5

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

Usage guidance is only implicit: use it to get a resort forecast. There is no explicit when-to-use versus alternatives, no mention of when another tool like get_snow_report or get_road_weather would be more appropriate, and no exclusions. It does mention tier and sign-in conditions, but those are access prerequisites rather than selection guidance.

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?