Skip to main content
Glama

List watches

list_watches
Read-onlyIdempotent

List saved title watches and optionally check live availability for each, so you can tell users whether a copy is available yet.

Instructions

List the title watches created with watch_title. Set check_now to also read each title's live availability, so you can tell the user whether a copy is available yet.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_watches"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_nowNoAlso fetch live availability for each watched title (up to 5).

Output Schema

NameRequiredDescriptionDefault
sourceYesProvenance of the data.
watchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A4.4/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 openWorld, so the safety profile is covered. The description adds meaningful behavior beyond that: check_now triggers live per-title lookups, which explains latency and external calls, and the 'up to 5' cap is reinforced in the schema.

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, front-loaded with the core action, then the option and its purpose. Nothing is redundant or padded.

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 an output schema present, return values need no explanation, and annotations cover safety. The description covers purpose and the optional mode well; minor gaps like whether all watches are returned or ordering are adequately handled by the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and there is only one parameter, so the baseline is 3. The description still adds value by framing check_now as a mode toggle with a user-facing rationale (reporting live availability) rather than just a flag definition.

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?

The description states a specific verb and resource ('List the title watches') and ties it to the creating sibling ('created with watch_title'), which cleanly separates it from watch_title itself and from check_availability.

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

Usage Guidelines4/5

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

It gives explicit conditional guidance for the one option ('Set check_now to also read each title's live availability') and explains the payoff ('tell the user whether a copy is available yet'). It does not name an alternative tool or state when not to use this one, which keeps it short of a 5.

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