Skip to main content
Glama
Sign In

ROVE Snow Forecast

by com.rove-ski
OverviewDiscussionsAdmin

Read Forecast Model Spread and Uncertainty

get_forecast_confidence
Read-onlyIdempotent

Evaluate weather-model agreement and horizon uncertainty for one ski resort's forecast; use get_forecast instead for daily and 3-hourly snowfall amounts. Diagnose model spread and days 1-3, 4-7, and 8-15 uncertainty, with unavailable values explicitly labeled. 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_forecast_confidence"
  }
}

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.3/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 non-open-world, so the safety profile is covered. The description adds behavior beyond that: unavailable values are explicitly labeled rather than dropped, results carry canonicalUrl and observedAt, and values are reported in inches for snowfall and Fahrenheit for temperature. It does not discuss pagination or latency, but these are minor for a single-resort read.

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?

Front-loaded with purpose and the sibling alternative, followed by diagnostic scope and then output conventions. It is dense and every clause carries information, though the single run-on sentence structure with semicolons makes it slightly harder to scan than a two- or three-sentence layout.

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 parameters, no nested objects, and no output schema, the description carries the return-value burden itself and does so reasonably — units, missing-data labeling, and result metadata fields are all named. Complete enough for an agent to call and interpret results correctly.

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 en/zh language switch are already documented in the schema. The description adds no syntax or semantics beyond that, which is the expected baseline when the schema does the heavy lifting.

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 — 'Evaluate weather-model agreement and horizon uncertainty for one ski resort's forecast' — and immediately contrasts it with the sibling get_forecast, which handles daily and 3-hourly snowfall amounts. An agent can distinguish this diagnostic tool from the forecast-retrieval tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use this tool for model spread and the 1-3, 4-7, 8-15 day uncertainty bands, and use get_forecast instead when actual snowfall amounts are needed. Both the when-to-use and the when-not-to-use are stated with a named alternative.

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