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 favourite resort when signed in.

Input Schema

TableJSON 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

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

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. Beyond that, the description adds useful behavioral context: forecasts are day-by-day, the default is 7 days, 14 days requires SnowSure Pro, and the signed-in state can affect behavior via a favourite resort. This is valuable context not present in 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?

A single front-loaded sentence contains the action, key result fields, and horizon. It is concise, but the trailing clause 'or for a favourite resort when signed in' is grammatically ambiguous and weakens an otherwise tight structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a complete input schema, annotations, and an output schema, most context is already supplied. However, the description leaves the favourite-resort behavior under-specified (how it is selected, whether slug/resort are optional when signed in), and there are no required parameters, which could leave an agent unsure about what to pass.

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 parameters are already documented (days default/max, slug vs resort formats). The description adds only a high-level hint that a favourite resort may be used when signed in, which is not enough to raise it above the baseline for fully covered schemas.

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 opens with a specific verb and resource: 'Get detailed day-by-day weather forecast for a resort', and enumerates the returned fields (temperature, snowfall, wind, conditions) and horizon. It is clearly distinguishable from siblings like get_snow_report or get_road_weather, though it never names a sibling explicitly, so it stops short of a fully differentiated 5.

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 implies the use case: call this when a day-by-day resort weather forecast is needed. It does not state when to prefer another tool, nor does it give exclusions or alternatives, so guidance is only implicit rather than explicit.

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?