SnowSure

Overview Schema Source Related Servers Discussions Admin

Lift-operation risk

get_operating_risk

Read-onlyIdempotent

Estimate ski lift operating risk over 48 hours using wind, visibility, wind chill, and heavy snow forecasts. Uses modeled guidance, not the resort's decision.

Instructions

Will the lifts run? A 48-hour operating-risk estimate from the Open-Meteo forecast — wind-hold (gusts), visibility, cold (wind-chill), and heavy-snow control delays. Modeled guidance, NOT the resort's own operating decision — always check live lift status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`slug`	Yes	Resort slug

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.

First observedv1.0.0Jul 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds valuable behavioral context: modeled guidance, not official, caveat to check live status. No contradictions.

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?

Two sentences perfectly front-loaded: first states purpose with key details, second adds critical caveat. No wasted words.

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?

Tool has output schema, and description covers purpose, time horizon, factors, and limitations. Complete for a risk-estimation tool among many siblings.

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?

Only one parameter 'slug' with schema description 'Resort slug'. Schema coverage is 100%, so description adds no extra meaning. Baseline 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?

Description clearly states the tool provides a 48-hour operating-risk estimate for lifts, listing specific factors (wind-hold, visibility, cold, heavy-snow). It distinguishes from both the resort's own decision and sibling tools like get_weather_forecast and get_snow_report.

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?

Explicitly states 'Modeled guidance, NOT the resort's own operating decision — always check live lift status.' This tells the agent when to use (risk estimate) and when not to rely solely on it, effectively guiding usage and alternatives.

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