Skip to main content
Glama

List watches

list_watches
Read-onlyIdempotent

Lists active and recently ended watches with their end reasons plus available webhook sink names, helping you find a watch ID or sink name before creating a watch.

Instructions

List this connection's watches (active and recently ended, with the reason they ended) and the names of the operator's webhook sinks a watch may use. Use it to find a watch_id or a sink name for create_watch; for what a watch has matched, use list_watch_events.

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
sinksNo
watchesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds non-obvious behavioral detail the annotations cannot: the listing includes recently ended watches and explains why they ended, and it also returns webhook sink names rather than only watches. It does not discuss ordering or limits, which keeps it at 4 rather than 5.

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?

A single dense sentence plus one routing sentence, with the primary scope stated first and the alternative named last. Every clause carries information an agent needs to select the tool or interpret its results.

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

Completeness5/5

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

For a zero-parameter read tool with an output schema and full annotation coverage, the description supplies the remaining gaps: what subset of watches is returned, that sink names come back too, and which siblings to use otherwise. Nothing required to call it correctly is missing.

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 no parameters, so there is no schema semantics to compensate for; the baseline for zero parameters is 4. The description appropriately spends its words on scope and routing instead of inventing argument detail.

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?

Specific verb and resource ('List this connection's watches') with an explicit scope qualifier ('active and recently ended, with the reason they ended') and an added return surface ('names of the operator's webhook sinks'). It explicitly separates itself from list_watch_events and points at create_watch as the consumer of its output.

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

Usage Guidelines5/5

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

Gives a concrete use case ('find a watch_id or a sink name for create_watch') and an explicit exclusion routing to a named alternative ('for what a watch has matched, use list_watch_events'). Nothing is left to inference about when to pick this tool.

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