Skip to main content
Glama

list_watches

View active watchers monitoring CI results, deployments, test outcomes, and file system changes in real-time.

Instructions

List all active watchers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handleListWatches method that executes the logic for the list_watches tool.
    private async handleListWatches() {
      const watches = this.registry.list();
      return {
        content: [{
          type: 'text' as const,
          text: JSON.stringify(watches, null, 2),
        }],
      };
  • src/server.ts:142-146 (registration)
    The registration of the list_watches tool definition within the MCP server.
    {
      name: 'list_watches',
      description: 'List all active watchers',
      inputSchema: { type: 'object', properties: {} },
    },
Behavior2/5

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

No annotations provided; description carries full burden but minimally discloses only the 'active' filter. Missing return format, pagination behavior, performance cost, or relationship to watch lifecycle states.

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?

Extremely efficient four-word description with zero redundancy. Front-loaded with action verb and contains no filler.

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?

Sufficient for a zero-parameter tool but leaves significant gap regarding return values since no output schema exists. Agent understands the action but not the structure or content of the watch list returned.

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?

Zero parameters present; baseline 4 applies per scoring rules. No parameter description required or provided.

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?

Clear verb (List) and resource (active watchers). The scope word 'all' and state 'active' help distinguish this aggregation tool from sibling creation tools (watch_file, etc.), though explicit contrast is absent.

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?

Provides no guidance on when to invoke versus alternatives like poll_events, or how the returned list should be used with cancel_watch. No prerequisites or conditions specified.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jarvisassistantux/loopsense'

If you have feedback or need assistance with the MCP directory API, please join our Discord server