Skip to main content
Glama

Season recap

season_recap
Read-onlyIdempotent

Summarise the most recent completed ski season from the local ERA5 archive first.

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

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

C2.9/5.0
Behavior3/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 the safety profile is covered. The description adds real value by disclosing the source (local ERA5 archive) and that the window is the most recent *completed* season, implying archival rather than live data. It says nothing about latency, coverage limits, or what the summary contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no padding, and the core scope is front-loaded. However, the dangling "first" is ambiguous — it reads like a fragment of a longer instruction rather than a self-contained definition.

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

Completeness2/5

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

The tool is simple (one required param, no output schema), but with no output schema the description is the only place an agent could learn what a "season recap" actually returns — snow totals, season length, comparisons? That is entirely absent, so an agent cannot anticipate the response shape or judge whether the call answers the user's question.

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% and the single resort parameter is documented with both a name and numeric-id example, so the schema does the heavy lifting. The description adds no additional meaning about the parameter (e.g., whether names are fuzzy-matched or whether an unknown resort errors).

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?

States a specific verb ("Summarise") and a specific resource ("the most recent completed ski season"), plus the data source ("local ERA5 archive"). That clearly separates it from live-condition siblings like get_conditions or get_forecast, though it never names an alternative explicitly.

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?

The trailing "first" hints at sequencing inside some larger workflow, but no condition for choosing this tool over get_forecast, get_extended_outlook, or snow_reliability is given, and no exclusions are stated. An agent must infer that this is for retrospective/historical season summaries.

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