Skip to main content
Glama

nws_public_witnessing_cancel_repeat_template

Cancel a pending public witnessing template repeat without writing changes, so unwanted recurring schedules are stopped before they are applied.

Instructions

Cancel a pending public witnessing template repeat without writing.

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": {
      "confirmation_id": "<confirmation_id>"
    },
    "name": "nws_public_witnessing_cancel_repeat_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Without writing' hints at a side-effect-free or discard-style operation but never explains what actually happens to the pending repeat, whether it is idempotent, whether it errors if the template is not pending, or what confirmation_id must contain.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no padding, so it is not verbose. But the final clause 'without writing' reads as an unresolved ambiguity rather than a useful qualifier, so brevity comes at the cost of clarity.

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

Completeness2/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 values need not be explained. Still, for a cancel tool in a preview/commit/cancel triad, the description leaves out the workflow position, confirmation_id provenance, and failure conditions — key gaps with zero annotation coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter confirmation_id has 0% schema description coverage, and the description adds nothing about it — not where to obtain it (presumably a preview call) nor what invalid values mean. With one undocumented parameter, the description must compensate and does not.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb and resource are identifiable ('Cancel a pending public witnessing template repeat'), which distinguishes it from the sibling commit/preview repeat-template tools. However, the trailing clause 'without writing' is opaque and undercuts an otherwise specific statement, leaving the agent unsure whether the tool actually mutates state or is a no-op.

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

Usage Guidelines2/5

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

No guidance on when to use this instead of nws_public_witnessing_preview_repeat_template or nws_public_witnessing_commit_repeat_template, nor on prerequisites (e.g., that a preview must exist first). The agent must infer the preview→commit/cancel workflow from sibling names alone.

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

Deploy Server

Other Tools