Skip to main content
Glama

yeastar_cancel_change

Read-only

Discards a prepared but not yet applied configuration change identified by its change ID, stopping the pending modification before it takes effect.

Instructions

Scarta una modifica preparata e non ancora applicata.

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": {
      "change_id": "<change_id>"
    },
    "name": "yeastar_cancel_change"
  }
}

Input Schema

NameRequiredDescriptionDefault
change_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, and the phrase "non ancora applicata" is consistent with that: only staged state is discarded, not live configuration. The description adds no error behavior (unknown or already-applied change_id), no idempotency note, and no indication that discarding is reversible by re-preparing.

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?

A single efficient sentence with no filler and the key constraint front-loaded. It is arguably too terse for a tool whose only parameter is unexplained, but nothing is wasted.

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?

Output schema exists so return values need not be described, and annotations carry the safety profile. Still missing is the provenance of change_id and the outcome when discarding fails, which matters for a one-parameter mutation of staged state.

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?

Schema description coverage is 0% for the single required change_id, and the description never mentions it — no hint about where change_id originates (e.g., from prepare_change or pending_changes) or its format. With one undocumented parameter, the description should compensate and does not.

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?

The description gives a specific verb plus resource: discarding ("scarta") a prepared change that has not yet been applied. The qualifier "non ancora applicata" separates it from applying a change, though it never names the sibling yeastar_apply_change or yeastar_pending_changes explicitly.

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?

The condition for use is implied by "prepared and not yet applied" — use it before a change is applied — but no explicit alternative is named and no guidance is given for what to do when the change is already applied or the change_id is unknown.

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