Skip to main content
Glama

list_watches

Lists watch statuses and outcomes to check active, completed, or needs_review results; needs_review cases require manual review and never retry automatically after uncertain purchases.

Instructions

Durable watch status/outcomes; needs_review never retries automatically after uncertain purchases.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does supply one genuinely non-obvious domain fact: watches in needs_review never retry automatically after uncertain purchases. However, it never states that this is a pure read with no side effects, nor whether results are paginated or bounded, and other watch states are left unexplained.

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?

Only two clauses, so there is no padding, and the resource is front-loaded. But the compression is aggressive to the point of being cryptic — 'Durable watch status/outcomes' is a noun fragment that costs the reader more than a short verb phrase would.

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?

The presence of an output schema means return values need not be explained, and zero parameters keeps the call surface simple. Still, for a zero-annotation tool the description omits the read-only nature, the full set of watch states, and any scoping of what 'watches' covers, leaving meaningful gaps.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The absence of parameters is consistent with a plain list/status retrieval.

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

Purpose3/5

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

The fragment 'Durable watch status/outcomes' identifies the resource (watches) and roughly what is returned (status and outcomes), but supplies no verb, so an agent must infer from the name that this is a read/list operation. It does not distinguish itself from siblings like cancel_watch or watch_meal beyond the implicit read semantics.

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 statement of when to call this tool, no prerequisites, and no mention of the alternatives in the sibling set (watch_meal, cancel_watch, menu, orders). The needs_review clause is a behavioral fact, not usage guidance, so the agent is left to infer invocation conditions.

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