Skip to main content
Glama

nws_public_witnessing_cancel_admin_change

Cancels a pending public witnessing administration preview so no changes are written. Use it to discard a staged edit before confirmation.

Instructions

Cancel a pending public witnessing administration preview 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_admin_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and "without writing" usefully discloses that no underlying data is mutated — valuable for a cancel operation. However it says nothing about whether the confirmation_id is invalidated, whether repeated calls are idempotent, or what state the preview is left in.

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?

One short sentence, front-loaded with the verb and resource, with no filler. The only cost is that "without writing" is terse enough to be mildly ambiguous about what is actually discarded.

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

Completeness3/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 not required, but for a cancel tool with no annotations and an undocumented required identifier, the description should at least state the confirmation_id's source and post-cancel effect. As it stands it is minimally sufficient to attempt a call but not to call it correctly with confidence.

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, so the description is the only place to explain it, and it does not — no origin (which preview tool produces it), format, or lifetime is given. The agent must guess where the value comes from.

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?

Names a specific verb (Cancel) and a specific resource (pending public witnessing administration preview), and the phrase "without writing" distinguishes it from the sibling nws_public_witnessing_commit_admin_change, which would apply the change. It is not explicitly contrasted with that 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 Guidelines2/5

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

The word "pending" hints that this follows a preview step, but the description never states when to cancel versus commit, nor names nws_public_witnessing_commit_admin_change as the alternative. There is no mention of what happens if the confirmation is stale, missing, or already consumed.

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