Skip to main content
Glama

snapshot_restore

Revert a VM to a specified snapshot. Preview with dry run to avoid irreversible data loss.

Instructions

[WRITE][risk=high] Revert a VM to a snapshot. Destructive & NOT undoable — preview first.

Reverting overwrites the VM's current state; pass dry_run=True to preview.
Tagged risk=high (audit tier 'review'); NUTANIX_AUDIT_APPROVED_BY /
NUTANIX_AUDIT_RATIONALE optionally annotate who/why.

Args:
    vm_ext_id: VM extId as returned by vm_list.
    snapshot_ext_id: Snapshot extId as returned by snapshot_list.
    dry_run: If True, preview the revert without performing it.
    target: Prism Central target name from config; omit for the default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetNo
dry_runNo
vm_ext_idYes
snapshot_ext_idYes
Behavior5/5

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

With no annotations, the description fully discloses destructive, irreversible behavior, mentions overwriting current state, and optional audit annotations. 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?

Well-structured: header line with key details, then expanded explanation, then parameter list. Concise and front-loaded.

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 action, risks, parameters, audit hints. Lacks mention of return values or post-revert state, but acceptable given no output schema.

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?

Provides clear explanations for all 4 parameters: vm_ext_id (from vm_list), snapshot_ext_id (from snapshot_list), dry_run (preview), target (default omit). Compensates for 0% schema description coverage.

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?

Clearly states verb 'Revert' and resource 'VM to a snapshot', distinguishes from siblings like snapshot_delete and vm_delete by emphasizing the destructive and irreversible nature.

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?

Advises to preview first using dry_run=True and notes risk=high as audit tier 'review', implying cautious use. Could explicitly compare to siblings but context is clear.

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/Nutanix-AIops'

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