Skip to main content
Glama

Watch resort

watch_resort
Read-onlyIdempotent

Return a one-tap EM Snow URL where the person can watch a resort and optionally add dates. This tool does not collect email.

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

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

A3.6/5.0
Behavior3/5

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

The annotations already establish a read-only, non-destructive, idempotent, closed-world operation, and the description is consistent with that. It adds genuinely useful behavioral detail beyond the annotations by stating that no email is collected and that the result is a shareable one-tap URL. It stops short of explaining link lifetime, whether the link is scoped to the caller, or what happens when the resort is unknown.

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 short sentences with the primary outcome front-loaded and the privacy clarification placed after it. Nothing is padded or repeated.

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?

For a one-parameter, read-only tool with no output schema, the description covers the essentials: what is produced (a URL) and one salient constraint (no email). The only shortfall is the dangling "optionally add dates" phrase, which is unexplained given that no dates parameter exists and could send an agent hunting for one.

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 coverage is 100% and the single parameter is fully documented, including that a resort name or numeric id from search_resorts is accepted, so the baseline is 3. The description adds no parameter-level meaning; its mention of "optionally add dates" does not correspond to any input field in the schema and could momentarily confuse an agent looking for a dates argument.

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 uses a specific verb and outcome: it returns a one-tap EM Snow URL that lets someone watch a resort. That is concrete enough to distinguish it from most siblings, but it never explicitly contrasts itself with adjacent tools such as search_resorts or get_webcams, leaving the agent to infer the boundary.

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

Usage Guidelines3/5

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

Usage is only implied: the tool is for watching a resort, and dates can optionally be added at the destination. There is no explicit statement of when to prefer this over search_resorts or get_webcams, and no prerequisites or exclusions are given.

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