Skip to main content
Glama

snapshot_revert

Revert a VM to a snapshot, permanently replacing its current state. Dry-run previews changes; audit-logged and irreversible, so snapshot first if you might return.

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

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
dry_runNo
snapshot_idYes
Behavior5/5

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

No annotations provided, but the description fully covers behavioral traits: marks the operation as WRITE with high risk, explicitly states it is IRREVERSIBLE, explains state replacement, and mentions audit capture. No contradictions.

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

Conciseness5/5

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

Four sentences plus three parameter lines, no wasted words. Key information is front-loaded in the first line. Every sentence contributes value.

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?

Covers purpose, parameters, and behavior well. However, no output schema is provided and the description does not mention return values or success indicators, which is a minor gap for contextual completeness.

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 description coverage is 0%, but the description provides detailed comments for all three parameters: snapshot_id ('Snapshot uuid to revert to', referencing snapshot_list), dry_run preview behavior, and target default behavior, adding significant meaning beyond the schema.

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?

The description clearly states 'Revert a VM to a snapshot' with a specific verb and resource, and includes a risk marker. This distinguishes it from sibling tools like snapshot_create and snapshot_delete.

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

Usage Guidelines4/5

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

Explicitly advises to take a fresh snapshot first if one may need to come back, implying when to use snapshot_create as a preparatory step. Does not explicitly list alternatives, but provides clear context for when to use this tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AIops-tools/XCPng-AIops'

If you have feedback or need assistance with the MCP directory API, please join our Discord server