CertPacket

Stop a recall watch

stop_watching_recalls

DestructiveIdempotent

Delete a recall watch list and everything it has seen. Pass the watchKey that watch_recalls returned. This cannot be undone.

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": {
      "watchKey": "<watchKey>"
    },
    "name": "stop_watching_recalls"
  }
}

Input Schema

Name	Required	Description	Default
`watchKey`	Yes	The key watch_recalls returned

Output Schema

Name	Required	Description	Default
`notice`	Yes
`status`	Yes
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 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, so the safety profile is covered. The description goes beyond that by naming exactly what is destroyed ('everything it has seen') and warning 'This cannot be undone,' which is genuinely useful scope information rather than a restatement.

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?

Three short sentences, zero waste, with the action and its destructive scope front-loaded and the parameter hint second. Nothing could be cut without losing information.

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-value explanation is unnecessary. For a single-parameter destructive operation, the description plus annotations supply everything needed to call it correctly and safely.

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?

Only one parameter, and schema coverage is 100%; the schema description ('The key watch_recalls returned') is nearly identical to the description's sentence. The description adds no format or validation meaning beyond the pattern already in the schema, 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?

States a specific verb and resource: delete the recall watch list. It also defines the scope of the deletion (the list plus everything it has seen), which is more than the name alone conveys.

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?

Explicitly ties invocation to the output of a named sibling tool ('Pass the watchKey that watch_recalls returned'), giving the agent a clear prerequisite and pairing. It stops short of stating when NOT to use it or what alternatives exist if the key is unavailable.

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

All CertPacket tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.