Skip to main content
Glama

proxmox_create_snapshot

Create a snapshot of a Proxmox VM by node and VM ID, naming it to preserve a restore point before updates or configuration changes.

Instructions

Create a snapshot of a Proxmox VM.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
nodeYes
vmidYes
gateway_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.72.5

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies a point-in-time capture. It does not say whether the VM must be running or stopped, whether snapshots can be stacked, whether existing state is affected, what permissions are required, or what the call returns on success or failure.

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

Conciseness3/5

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

A single well-formed sentence with zero filler and the resource front-loaded. Its brevity, however, crosses into under-specification rather than efficient conciseness, since nothing beyond the name is restated with added value.

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?

For a four-parameter mutation tool with no annotations and no output schema, the description is far from sufficient. The agent knows what will be created but not the constraints, side effects, or required parameter semantics needed to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% across four parameters (vmid, node, name, gateway_id), and the description adds no meaning to any of them. In particular the purpose of the optional 'gateway_id' and the semantics of 'name' (uniqueness, conflict behavior) are left entirely unexplained.

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 states a specific verb and resource ('Create a snapshot of a Proxmox VM'), which tells an agent exactly what the tool does and that it targets Proxmox VMs specifically. It does not, however, explicitly differentiate itself from the similarly-named siblings such as vsphere_create_snapshot or vme_create_snapshot, leaving platform disambiguation to the tool name and prefix.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must infer from the name alone that this is the Proxmox-specific snapshot tool rather than the vSphere or XO equivalents.

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