SnowSure — Snow & Ski

Road & chain control

get_road_access

Read-onlyIdempotent

Driving access for a resort — answers "do I need chains to get to " and "is the road to open": a SnowSure drive call, feeder-city Saturday drive times on the PGRI pilot, plus chain-control / mountain-pass / road-surface conditions on nearby highways (California via Caltrans, Washington via WSDOT, Oregon via ODOT TripCheck, Montana via MDT 511, Wyoming via WYDOT 511, Colorado via CDOT, Utah via UDOT, British Columbia via DriveBC, Ontario via Ontario 511, New England via Compass C2C, Virginia via VDOT 511, New Zealand via NZTA). Returns 'no road data' outside the covered area. Links to the official DOT map; the resort's road status is authoritative.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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"
-]
```

AddedJun 25, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds valuable context beyond that: it is a SnowSure drive call, lists the specific highway data sources by state/province, and notes the authoritative nature of the resort's road status plus links to DOT maps. This enriches the safety profile without contradicting 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 long but information-dense, starting with the primary purpose and then systematically covering data sources and caveats. Every sentence adds value; there is no filler. It is appropriately detailed for a tool with broad geographic scope, though it could be tightened without losing clarity.

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 complexity of multiple data sources and output schema availability, the description covers coverage areas, fallback behavior, and authoritative status. It does not explain the exact output structure, but an output schema exists, so that is not required. The description is sufficient for an agent to decide when to call and what to expect.

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% and both parameters (slug and resort) are documented as the same resort identifier with examples and mutual exclusivity. The description does not add any new parameter-level detail, so it stays at the baseline of 3 – the schema already handles parameter semantics fully.

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 clearly states the tool provides driving access for a resort, answering two specific questions: chain requirements and road openness. It enumerates the exact data sources and geographic coverage, making it unmistakable what the tool does and how it differs from generic travel or weather tools.

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

Usage Guidelines4/5

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

The description implies when to use it: when the agent needs road access or chain-control info for a resort. It explicitly states the coverage areas and the fallback 'no road data' outside them. It does not name sibling tools like get_road_cameras or get_road_weather, but the clear scope lets an agent infer the appropriate alternative, so guidance is strong but not 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?