Skip to main content
Glama
Sign In
AIops-tools

xcpng-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

snapshot_revert

Destructive

Revert a VM to a chosen snapshot to restore its previous state; this replaces the current VM state irreversibly, so create a new snapshot first if rollback may be needed.

Instructions

[WRITE][risk=high] Revert a VM to a snapshot. IRREVERSIBLE.

The VM's CURRENT state is replaced by the snapshot — take a fresh snapshot
first (snapshot_create) if you may need to come back. Captures the
snapshot's state for the audit record; declares no undo.

Args:
    snapshot_id: Snapshot uuid to revert to (see snapshot_list).
    dry_run: If True, preview without reverting.
    target: Xen Orchestra target name from config; omit for the default.

Input Schema

NameRequiredDescriptionDefault
targetNo
dry_runNo
snapshot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds the critical operational facts: the operation is IRREVERSIBLE, the VM's current state is replaced, and no undo is declared. This goes well beyond what the annotations convey.

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?

The risk warning is front-loaded ahead of everything else, which is exactly right for a destructive tool, and the Args block is compact. Minor slack in the audit-record sentence, which is informative but slightly vague about what is being captured.

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?

For a high-risk mutation with no output schema, the description covers safety profile, reversibility, prerequisites, a safe preview path, and every parameter. Nothing an agent needs to avoid a destructive mistake is missing.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden — and it does: snapshot_id is a snapshot uuid (source: snapshot_list), dry_run previews without reverting, and target is the Xen Orchestra target name from config with an explicit omit-for-default rule.

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+resource ('Revert a VM to a snapshot') and immediately scopes it with [WRITE][risk=high]. It is clearly distinguishable from the sibling snapshot_create/snapshot_list/snapshot_delete tools, which it names directly.

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

Usage Guidelines5/5

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

Explicitly tells the agent when NOT to use it carelessly ('take a fresh snapshot first (snapshot_create) if you may need to come back') and offers a safe alternative path via dry_run. Routes the agent to snapshot_list for obtaining the id.

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