Skip to main content
Glama
Sign In
Kiln

Kiln

by codeofaxel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

stop_watch_print

Destructive

Stop a running background print watcher by its watch ID, return its final state, and remove it from the active watchers registry.

Instructions

Stop a background print watcher and return its final state.

        Signals the watcher thread to exit and removes it from the
        active watchers registry.

        Args:
            watch_id: The watcher ID returned by ``watch_print``.

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": {
      "watch_id": "<watch_id>"
    },
    "name": "stop_watch_print"
  }
}

Input Schema

NameRequiredDescriptionDefault
watch_idYesThe watcher ID returned by ``watch_print``.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.5.1
    • addedInput schema / properties / watch_id / description
      Added value: +"The watcher ID returned by ``watch_print``."
  2. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Despite destructiveHint=true already being declared, the description adds real context: the watcher thread is signaled to exit and the entry is removed from the active watchers registry, and the final state is returned. It does not say what 'final state' contains or how errors/unknown IDs are handled, which keeps it from a 5. The stopping action is consistent with the destructive annotation, not contradicted by it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short descriptive sentences front-load the effect and return, then a minimal Args block. The Args line duplicates the schema at slight cost, but nothing else is wasted.

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 single-parameter tool the definition is nearly sufficient, but with no output schema the phrase 'return its final state' is left undefined — the caller cannot know the shape of that state or what happens on an unknown watch_id.

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?

Schema coverage is 100% and the description's Args note ('the watcher ID returned by watch_print') is essentially verbatim what the schema already documents, so no meaning is added beyond the structured field. Baseline 3 applies when the schema carries the parameter semantics.

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?

The description gives a specific verb and resource ('Stop a background print watcher') plus the side effect of returning the final state, which clearly separates it from the watch_print/watch_print_status siblings that create or poll a watcher. It stops short of an explicit contrast with watch_print_status, so a 4 rather than a 5.

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?

Use is only implied: it is the teardown counterpart to watch_print, and the parameter doc ties the call to a previously created watcher. It never states when to stop versus keep polling with watch_print_status, nor whether calling it on a nonexistent/already-stopped watcher is safe.

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

Deploy Server

Other Tools