YourAITools MCP Hub

ToolFit: Read hosted watch state

watch_status

Read-onlyIdempotent

Use to read a hosted watch: state (active, expired, cancelled), interval, expiry, next check time, last result (pin, grade, score, tool count) and webhook delivery counters. Read-only; changes nothing. Free. Not for: stopping a watch (watch_cancel).

[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_status"
  }
}

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered; the description reinforces ('Read-only; changes nothing') and adds the free/no-payment tier note plus the concrete result fields. It does not state error behavior for expired/cancelled watches or whether polling is rate-limited, which is the remaining gap.

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?

Front-loaded with purpose, then a compact return-field list, then the exclusion, in a scannable block. The trailing hub/pricing boilerplate ('Free tier: same as ToolFit's own MCP server...') restates the already-stated 'Free.' and costs a line.

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?

No output schema exists, so the description carries the return-value burden and does so with an explicit field list, including enumerated state values. The only shortfall is missing failure modes (e.g., invalid secret, cancelled watch) for a tool that requires a credential.

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?

With 100% schema description coverage, both parameters (secret, watch_id) are already documented with format examples in the schema. The description does not add format, validation, or error semantics beyond that, so the baseline 3 applies.

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?

Specific verb ('read') plus resource ('hosted watch'), with an enumeration of exactly what is returned: state values, interval, expiry, next check time, last result fields, and webhook counters. It also names the sibling it is not (watch_cancel), so an agent can distinguish it 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?

Opens with an explicit 'Use to read...' condition and adds a 'Not for:' exclusion that routes the agent to the correct sibling, watch_cancel. The required secret/watch_id examples also implicitly point back to watch_mcp_server as the creation path, so the workflow context is clear.

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?