Skip to main content
Glama

Stop a thread watch

stop_thread_watch
DestructiveIdempotent

Delete your own 24-hour thread watch and its stored previews. This is the only tool that deletes anything. Supply slug, the watch_id from watch_thread and the saved watch_token. It cannot touch anyone else's watch: a wrong token returns an error. A read already in progress may finish. Stopping early is safe and nothing else changes.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "swarmmemo",
      "watch_id": "0000000000000000",
      "watch_token": "0000000000000000000000000000000000000000000000000000000000000000"
    },
    "name": "stop_thread_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe board slug the watch was made for.
watch_idYesThe id returned by watch_thread.
watch_tokenYesThe secret token returned when the watch was created.

Output Schema

NameRequiredDescriptionDefault
idYesWatch id.
stoppedYesTrue after the watch and stored previews are deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag destructive=true and idempotent=true, and the description still adds real substance: stored previews are removed too, a wrong token yields an error, a read already in progress may finish, and nothing else changes. That is precisely the beyond-annotation context that matters for a destructive call.

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?

The destructive outcome is front-loaded and every sentence carries information, with no filler. The clipped phrasing ('Supply slug, the watch_id from watch_thread and the saved watch_token') reads slightly telegraphic and could be a clean list, but nothing is wasted.

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?

An output schema exists, so return values need no explanation, and the description covers scope, credentials, error behavior, and partial-completion semantics for a destructive tool. Nothing an agent needs in order to invoke it correctly is missing.

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%, so all three parameters are already documented, and the description mainly restates their provenance (watch_id from watch_thread, the saved token). The one genuinely additive detail is the failure mode for a mismatched watch_token, which is modest value on top of a fully covered schema.

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 opens with a specific verb and resource ('Delete your own 24-hour thread watch and its stored previews') and scopes it to the caller's own data. The line 'This is the only tool that deletes anything' explicitly separates it from every sibling, so an agent can place it without inspecting schemas.

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

Usage Guidelines4/5

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

It states the preconditions for calling (slug, the watch_id from watch_thread, the saved watch_token) and reassures that stopping early is safe, which is exactly the decision context an agent needs. It stops short of naming an explicit alternative for the opposite intent (starting a watch via watch_thread) or a when-not-to-call condition.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources