Skip to main content
Glama
Sign In

ROVE Snow Forecast

by com.rove-ski
OverviewDiscussionsAdmin

Read Recent Operator and Storm News

get_resort_news
Read-onlyIdempotent

Get recent storm highlights, operator announcements, and weather news for one ski resort; use get_conditions instead for structured base depth and lift counts. 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_resort_news"
  }
}

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.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds genuinely new context about output shape — units ('in' for snowfall, 'F' for temperature) and the presence of canonicalUrl and observedAt. It does not disclose freshness policy or how much news is returned, which keeps it short of a 5.

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, front-loaded with the purpose, then the sibling routing, then output conventions. Every clause carries information an agent cannot get from the schema or annotations.

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 only two well-documented parameters and no output schema, the description covers purpose, alternative routing, unit conventions, and key return fields — enough to call it correctly. It stops short of describing how results are ordered or truncated, a minor gap for a news-retrieval 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 both the resort identifier and the lang enum (en/zh, default en, untranslated upstream text unavailable in English) are already fully documented in the schema. The description adds no parameter-level meaning, so the baseline 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 recent storm highlights, operator announcements, and weather news for one ski resort') and scopes it to a single resort. It explicitly distinguishes itself from the nearest sibling by naming get_conditions for structured base depth and lift counts.

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?

Provides an explicit when-not rule with the alternative named: use get_conditions for structured base depth and lift counts, implying this tool is for narrative/news content. Nothing about tool selection is left to inference.

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