Skip to main content
Glama

Stop a page watch

stop_watch
DestructiveIdempotent

Stop a page watch and delete the stored copy of the page. Use it when the watch is no longer needed.

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": {
      "id": "<id>"
    },
    "name": "stop_watch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWatch id returned by watch_page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Id returned when the job was created"New value: +"Watch id returned by watch_page."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so safety is covered. The description adds the nontrivial detail that the stored page copy is destroyed, which tells the agent the deletion is irreversible in terms of stored data — value beyond the structured fields, though nothing is said about permissions or post-delete state.

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?

Two short sentences with zero filler; the destructive side effect is front-loaded ahead of the usage condition.

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

Completeness4/5

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

For a one-parameter, well-annotated mutation with no output schema, the description covers what happens and when to call it. A note on reversibility or required ownership would close the last gap, but nothing essential is missing for correct invocation.

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 single 'id' property is documented in the schema as coming from watch_page, with a pattern constraint. The description adds no further meaning about the id, so baseline 3 applies.

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?

States a specific verb and resource ("Stop a page watch") plus the concrete consequence ("delete the stored copy of the page"), which implicitly makes it the inverse of watch_page. It lacks an explicit contrast with siblings like get_watch or check_watch_now, but the action is unambiguous.

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 it when the watch is no longer needed" gives a minimal trigger condition but no exclusions (e.g., pause vs. destroy) and no mention of alternatives for managing an unwanted watch. Usage is implied rather than fully specified.

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.