YourAITools MCP Hub

ToolFit: Stop a hosted watch early

watch_cancel

DestructiveIdempotent

Use to stop a hosted watch now: no further checks or webhooks are sent. Irreversible; remaining days are not refunded. Free. Not for: reading progress or results (watch_status).

[ToolFit via YourAITools MCP Hub] Free tier: same as ToolFit's own MCP server (call without payment and without tier). Free.

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>",
      "secret": "<secret>"
    },
    "name": "watch_cancel"
  }
}

Input Schema

Name	Required	Description	Default
`secret`	Yes	The whsec_... secret returned once when the watch was created
`watch_id`	Yes	watch_id (w_...) returned by POST /v1/watch

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026
- addedInput schema / properties / secret / examples
```
Added value: +[
+  "whsec_<secret returned by watch_mcp_server>"
+]
```
- addedInput schema / properties / watch_id / examples
```
Added value: +[
+  "w_<24 hex from watch_mcp_server>"
+]
```
AddedOct 24, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds consequences the flags cannot express: webhooks stop being sent, the action cannot be undone, and unused time is not refunded. That irreversibility language is consistent with idempotency (repeat calls are no-ops), not contradictory. Only gap is that it does not mention the secret/credential needed, though the schema covers that.

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 core sentence is front-loaded and the exclusion follows immediately, so the important information is first. However, the pricing statement "Free" appears twice plus a full hub/free-tier boilerplate line, which is redundant weight that does not help the agent invoke the tool.

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 2-parameter, no-output-schema tool with rich annotations, the description covers purpose, consequence, irreversibility, and the sibling it does not replace. Only minor omission is any note on calling it against an already-cancelled watch, though idempotentHint largely covers that.

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 description coverage is 100% with only two parameters, both already documented with examples (w_... watch_id, whsec_... secret), so the schema carries the semantic weight. The description adds no additional detail about either parameter, which is the baseline-3 case.

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?

Names a specific verb and resource ("stop a hosted watch now") and states the immediate consequence ("no further checks or webhooks are sent"). It explicitly distinguishes itself from the closest sibling, watch_status, so an agent can separate the two without opening either schema.

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

Usage Guidelines5/5

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

Gives both a when-to-use clause ("Use to stop a hosted watch now") and an explicit exclusion that names the alternative ("Not for: reading progress or results (watch_status)"). Nothing about routing between this tool and watch_status is left to inference.

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

All YourAITools MCP Hub tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?