The MCP Census

Remove a server watch

census_watch_unsubscribe

DestructiveIdempotent

Deactivate a watch by id. Requires x-api-key that owns the watch.

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": "census_watch_unsubscribe"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Watch id from census_watch_subscribe

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 1, 2026

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 and idempotentHint=true, and the description adds genuinely new context: the call requires an x-api-key that owns the watch. It could go further by clarifying what 'deactivate' means versus permanent deletion and whether the watch data is retained.

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, the action and its scope front-loaded, followed by the auth constraint. Nothing is wasted.

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, non-read-only tool with no output schema, the description plus annotations cover safety profile and auth prerequisites adequately. Only the semantics of deactivation versus deletion remain unstated.

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 parameter is documented as coming from census_watch_subscribe, so the schema does the heavy lifting. The description only restates 'by id' and adds no format or sourcing detail beyond the schema.

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 (deactivate) and resource (watch) scoped by id, which clearly separates it from the sibling census_watch_subscribe. It doesn't explicitly name the counterpart sibling, but the operation 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?

Usage is implied by the verb — you call it to remove a watch — but there is no explicit guidance such as needing to fetch the id via census_watch_list first, or any note on when to prefer this over other cleanup paths.

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

All The MCP Census 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?