Skip to main content
Glama

yeastar_prepare_rollback

Read-only

Prepares rollback of an applied PBX configuration change using its saved snapshot: restores previous values, removes created objects, or recreates deleted ones.

Instructions

PREPARA l'annullamento di una modifica già applicata, usando lo snapshot salvato: ripristina i valori precedenti (update), elimina l'oggetto creato (create) o lo ricrea (delete).

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_prepare_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
change_idYeschange_id di una modifica già applicata

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description is consistent with a preparation step ('PREPARA'), but the clause 'elimina l'oggetto creato' can be misread as an immediate deletion. Useful added context is that the rollback is driven by a saved snapshot; still missing is the precondition that a snapshot must exist and that the rollback only takes effect once applied via another tool.

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 sentence, front-loaded with the all-caps 'PREPARA' so the staging nature is the first thing read. The parenthetical type mapping is compact and earns its space, though the sentence is dense and mixes Italian prose with English keywords.

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?

Moderate complexity, one required parameter and an existing output schema (so return values need not be described), and the description covers the core mechanics per change type. It is slightly short of complete because the two-stage flow and the dependency on a stored snapshot being available are not stated, which an agent needs to call this correctly in sequence.

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?

There is only one parameter and schema coverage is 100%, with the schema already defining change_id as 'change_id di una modifica già applicata'. The description adds only the implicit constraint that the change must be one with a saved snapshot, which is marginal value over the schema baseline of 3.

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 and resource ('PREPARA l'annullamento di una modifica già applicata') and even enumerates the three rollback transformations keyed to change type (update→restore, create→delete, delete→recreate). It never distinguishes itself from siblings such as yeastar_apply_change or yeastar_cancel_change, so an agent cannot tell from this text alone which tool actually commits or discards the prepared rollback.

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 only implied: the reader infers 'call this to undo an already applied change'. There is no statement about what must happen next (applying the prepared change) nor any exclusion or alternative, such as when to cancel a pending change instead.

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