Skip to main content
Glama
Sign In

ROVE Snow Forecast

by com.rove-ski
OverviewDiscussionsAdmin

Rank Resorts for Explicit Trip Dates

plan_trip
Read-onlyIdempotent

Rank ski resorts for a specific calendar trip window (start to end in YYYY-MM-DD); use find_powder instead for rolling next-N-days rankings starting today. 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": {
      "start": "<start>",
      "end": "<end>"
    },
    "name": "plan_trip"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesExplicit last trip date, YYYY-MM-DD, inclusive and on or after start. Required.
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 results returned. Default 20; full membership counts are reported separately.
startYesExplicit first trip date, YYYY-MM-DD. Required; dates use the resort local calendar.
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.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety and repeatability are covered by structured data. The description's added value is the output contract (snowfall in inches, temperature in Fahrenheit, plus canonicalUrl and observedAt) since there is no output schema. It says nothing about pagination behavior beyond the schema's offset/limit or how rankings are computed, leaving moderate gaps.

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 compact sentences with the primary scope front-loaded, then the sibling alternative, then the output contract. Every clause carries information; nothing is padding.

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?

With 8 parameters, full schema coverage, rich annotations, and no output schema, the description supplies the two things structured fields cannot: the unit conventions and returned identity fields, plus the sibling routing. Ranking methodology and result-ordering semantics remain unexplained, a minor gap for a ranking 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 description coverage is 100%, so every one of the 8 parameters (including lang, pass, region, country, limit, offset) is already documented in the schema. The description only restates the date format and units, adding no semantics the schema lacks — 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 (rank), resource (ski resorts), and scope (explicit calendar trip window with start/end in YYYY-MM-DD), and explicitly distinguishes itself from the find_powder sibling. An agent can identify the operation and its boundary without opening either schema.

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?

Explicitly routes the agent to find_powder when it needs rolling next-N-days rankings starting today, which is a real decision fork for the primary input. Missing guidance on when to prefer compare_resorts, search_resorts, or get_conditions, but the main ambiguity is resolved.

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