Skip to main content
Glama
Sign In

ROVE Snow Forecast

by com.rove-ski
OverviewDiscussionsAdmin

Fetch ROVE Resort or Hub Live Document

fetch
Read-onlyIdempotent

Fetch the full structured ROVE document and canonical URL for a resort:, region:, or pass: identifier returned by search; use get_forecast or get_conditions instead for targeted resort queries. Only internal catalog and cached documents are resolved; arbitrary external URLs are never fetched. 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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesKnown resort:<slug/name>, region:<slug>, pass:<slug>, name, slug or canonical https://rove-ski.com/en/r/<encoded-name> URL. Never an arbitrary URL.
langNoOutput language: en or zh. Default en; untranslated upstream text is unavailable in English.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), but the description adds real behavior: resolution is limited to the internal catalog and cached documents, external URLs never fetched, and results carry canonicalUrl, observedAt, with units in inches and degrees F. It stops short of saying what happens on an unknown or ambiguous identifier (error vs. nearest match).

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?

Three tight sentences, front-loaded with the primary action and followed by the sibling routing rule and the scope constraint. The trailing units sentence is useful but slightly compressed, packing two unit conventions plus two return fields into one clause.

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?

No output schema exists, and the description compensates by naming the key returned fields (canonicalUrl, observedAt) and the measurement units. With only two parameters and full schema coverage, the main remaining gap is failure/ambiguity behavior for unrecognized identifiers.

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 the schema already enumerates accepted id forms (resort:/region:/pass: slug, name, slug, canonical URL) and the en/zh lang enum. The description restates the identifier namespaces and adds only the workflow cue that ids come from search, so baseline 3 is appropriate.

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 (fetch) and resource (full structured ROVE document plus canonical URL) and enumerates the accepted identifier namespaces (resort:, region:, pass:). It explicitly names the sibling tools (get_forecast, get_conditions) it is not for, so an agent can distinguish it without opening any 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?

Gives explicit routing: use get_forecast or get_conditions for targeted resort queries, and use this tool for the full document on an identifier returned by search. Also states a hard negative condition — arbitrary external URLs are never fetched — which bounds misuse.

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