Skip to main content
Glama
Sign In

ROVE Snow Forecast

by com.rove-ski
OverviewDiscussionsAdmin

Find Ski Resorts by Name, Region or Pass

search_resorts
Read-onlyIdempotent

Search the structured catalog of 667 ski resorts by name, region, pass, or country; use search instead for natural-language keyword discovery across resorts and regional/pass hubs. Read-only results use in for snowfall, F for temperature, and include canonicalUrl and observedAt.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_resorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoOutput language: en or zh. Default en; untranslated upstream text is unavailable in English.
passNoMulti-resort pass filter. Default all passes when optional; legacy names and MC are normalized.
limitNoMaximum catalog matches. Default 50.
queryNoResort name or region substring. Default no text filter.
offsetNoZero-based result offset for pagination. Default 0.
regionNoRegion name or hub slug, such as Lake Tahoe or tahoe. Default all regions.
countryNoISO country filter. Default all countries.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already establish that this is read-only, idempotent, non-destructive, and closed-world. The description adds useful result context beyond annotations, including snowfall units in inches, temperature units in Fahrenheit, and fields like canonicalUrl and observedAt, though it does not cover all return fields.

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 are tightly front-loaded: purpose and catalog scope first, then the alternative tool, then result conventions. There is no filler or redundant repetition of the schema.

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?

For a seven-parameter, fully documented search tool with no output schema, the description supplies catalog size, the key alternative tool, and result units/fields. Nothing critical for correct invocation is missing.

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 parameter meanings are already fully documented. The description mentions name, region, pass, and country filters, but adds no syntax or semantics beyond what the schema provides.

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 states a specific verb and resource: searching the structured catalog of 667 ski resorts by name, region, pass, or country. It also explicitly distinguishes this tool from the sibling search tool, which handles natural-language keyword discovery.

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?

It gives an explicit alternative: use search instead for natural-language keyword discovery. Combined with the structured-filter framing of search_resorts, an agent can select between the two without opening either schema.

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