Skip to main content
Glama

Best time to go

best_time_to_go
Read-onlyIdempotent

Get historical snow odds from the local ERA5 archive and quiet-week guidance where the crowd scorer covers the resort.

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": "best_time_to_go"
  }
}

Input Schema

NameRequiredDescriptionDefault
resortYesResort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resort / description
      Added value: +"Resort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)"
  2. First observed

TDQS

B3.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 closed-world scope, so safety is covered. The description adds genuinely new behavior: the data provenance (local ERA5 historical archive) and, importantly, that the quiet-week portion is only returned for resorts the crowd scorer covers — an agent should know results can be partial.

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?

A single front-loaded sentence with no filler; the two outputs and the coverage caveat are packed efficiently. The compressed jargon ('ERA5 archive', 'crowd scorer') costs a little readability but no sentences are wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only tool with full annotation coverage and no output schema, the description covers what is produced and when output may be partial. It still leaves 'snow odds' and 'quiet-week guidance' undefined in form or units, which matters since no output schema exists to fill that gap.

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?

Only one parameter exists and schema coverage is 100%, with the schema already documenting that a name like 'Zermatt' or a numeric id from search_resorts is accepted. The description adds nothing about the resort argument, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names two concrete outputs — historical snow odds and quiet-week guidance — so an agent can tell this is an advisory/planning tool rather than a live-conditions tool. It does not explicitly distinguish itself from nearby siblings such as snow_reliability or season_recap, and jargon like 'ERA5 archive' and 'crowd scorer' is left unexplained.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says whether this should be called instead of snow_reliability, season_recap, or get_extended_outlook. The only conditional statement ('where the crowd scorer covers the resort') describes result coverage, not invocation guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources