Skip to main content
Glama
Sign In
Proxmox MCP Server

Proxmox MCP Server

by fredriksknese
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rollback_vm_snapshot

Destructive

Rollback a virtual machine to a specified snapshot to restore its previous state. Requires node, VM ID, and snapshot name.

Instructions

Rollback a VM to a snapshot

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": {
      "node": "<node>",
      "vmid": "<vmid>",
      "snapname": "<snapname>"
    },
    "name": "rollback_vm_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeYesThe node name
vmidYesThe VM ID
snapnameYesThe snapshot name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

The description adds no behavioral context beyond the destructiveHint annotation. It does not disclose whether the VM must be stopped, if the operation is reversible, or what happens to the current state. Since annotations already indicate destructiveness, the description fails to provide additional transparency.

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 description is extremely concise (one sentence, six words). It is front-loaded with the core action. However, it may be under-specified, which slightly reduces the score from perfect.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the operation's destructive nature, the description lacks critical context: effects on the running VM, need for shutdown, or what the result is. No output schema exists, so return values are unexplained. The description is incomplete for safe usage.

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?

The input schema already provides full descriptions for all three parameters (100% coverage). The description adds no extra meaning beyond what the schema offers, so a baseline score of 3 is appropriate.

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 the action and target: 'Rollback a VM to a snapshot'. It uses a specific verb and resource, and distinguishes this from sibling tools like create_vm_snapshot or delete_vm_snapshot.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. It does not mention prerequisites, such as the VM needing to exist or the snapshot needing to be current, nor does it advise when not to use it.

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