Skip to main content
Glama
Sign In

ROVE Snow Forecast

by com.rove-ski
OverviewDiscussionsAdmin

Read California Chain Controls Near a Resort

get_road_conditions
Read-onlyIdempotent

Get live Caltrans chain-control status (R-0 to R-3) and road closures on state highways near one California or Lake Tahoe ski resort; use get_conditions instead for on-mountain snow depth and lifts, and get_forecast for upcoming snowfall. Groups Caltrans CWWP2 checkpoints by route (for example US-395 at Mammoth, I-80 and SR-89 at Palisades Tahoe) with nearest distance, worst status and status time (cached up to 15 minutes). Outside California it returns not_covered plus the official state or provincial road information link, never an invented status. Read-only results use in for snowfall, F for temperature, and include canonicalUrl and observedAt.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "resort": "<resort>"
    },
    "name": "get_road_conditions"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: en or zh. Default en; untranslated upstream text is unavailable in English.
resortYesResort name, slug, or resort: ID from search_resorts. Required unless explicitly optional.
radius_kmNoSearch radius in kilometers around the resort for Caltrans checkpoints. Default 45.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavior: results are grouped by route with nearest distance and worst status, data is cached up to 15 minutes, and out-of-state queries return not_covered plus an official link rather than a fabricated status. That last point is a valuable anti-hallucination guarantee, though the description could say more about failure modes when no checkpoints fall inside the radius.

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?

Purpose, alternatives, and geographic caveat are front-loaded in the first two sentences, and every sentence carries operational information. It is dense in a single block, and the units/canonicalUrl sentence could be trimmed or split, but nothing is wasted or redundant.

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?

With no output schema, the description carries the return-value burden and does so: it describes route grouping, worst status, status time, distance, units (in/F), canonicalUrl, observedAt, and the not_covered sentinel. Combined with full parameter documentation and safe annotations, an agent has everything needed to call and interpret this tool.

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 coverage is 100%, so resort, radius_km, and lang are already fully documented with enums, bounds, and examples. The description reinforces the resort semantics ('one California or Lake Tahoe ski resort') and the returned distance metric, but adds no format or syntax detail beyond the schema, so the baseline of 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?

States a specific verb and resource ('Get live Caltrans chain-control status (R-0 to R-3) and road closures on state highways'), then constrains scope to one California or Lake Tahoe ski resort. It immediately distinguishes itself from get_conditions and get_forecast, so an agent can route without opening a schema.

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 names both alternatives and the condition that selects them: get_conditions for on-mountain snow depth and lifts, get_forecast for upcoming snowfall. It also states the geographic boundary where this tool applies and what happens outside it, leaving no ambiguity about when to call it.

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

All ROVE Snow Forecast toolsInspect
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