Skip to main content
Glama

watcher_stop

Stop a running hot folder watcher by its ID to halt automated folder monitoring. Use it to end a specific watcher process when it is no longer needed.

Instructions

Stop a running hot folder watcher by its ID.

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": {
      "watcher_id": "<watcher_id>"
    },
    "name": "watcher_stop"
  }
}

Input Schema

NameRequiredDescriptionDefault
watcher_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden but discloses only the basic state-changing effect of stopping a watcher. It does not explain whether shutdown is graceful or forced, what happens to active work or monitoring configuration, whether the watcher can be restarted, or what errors and results to expect.

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?

The single sentence is front-loaded with the action and contains no redundant or irrelevant wording. It communicates the core operation efficiently.

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?

For a simple one-parameter operation, the description is sufficient to understand the basic invocation when an ID is already known. Given the absence of annotations and an output schema, the missing ID-discovery guidance, shutdown semantics, and error behavior leave meaningful operational gaps.

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?

The phrase "by its ID" partially compensates for the schema's lack of parameter descriptions by clarifying that watcher_id identifies the watcher, rather than being a path or display name. It adds no information about ID format, provenance, or validity constraints.

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 gives a specific verb and resource—stopping a running hot folder watcher—and specifies that the watcher is selected by ID. The running-state qualifier and stop action clearly distinguish its function from starting or listing watchers.

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?

The wording implies that the target should already be running and that the caller must know its ID. However, it gives no explicit workflow for obtaining the ID, no prerequisites, and no guidance on handling an already-stopped watcher or choosing an alternative.

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