Proxmox MCP Server

create_container_snapshot

Create a container snapshot in Proxmox to preserve its current state. Snapshots allow quick restoration or serve as backups.

Instructions

Create a container 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": "create_container_snapshot"
  }
}

Input Schema

Name	Required	Description
`node`	Yes	The node name
`vmid`	Yes	The container VMID
`snapname`	Yes	The snapshot name
`description`	No	Snapshot description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 12, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description 'Create a container snapshot' is consistent with annotations (destructiveHint=false). However, it does not disclose any behavioral traits such as whether the container must be running, if the snapshot is incremental, or if existing snapshots with the same name are overwritten. With annotations present, this still lacks necessary context.

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 a single, short sentence with no unnecessary words. It effectively communicates the core action, though it could be slightly expanded without becoming verbose.

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 that there is no output schema and the tool has 4 parameters with high coverage, the description should provide more context about the snapshot creation process, such as whether it returns the snapshot ID, any prerequisites, or success indicators. It is incomplete for making fully informed decisions.

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 covers all 4 parameters (node, vmid, snapname, description) with descriptions. The tool description does not add any additional meaning beyond what the schema provides, so it meets the baseline for high schema coverage.

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 clearly states the verb 'create' and resource 'container snapshot', distinguishing it from sibling tools like 'create_vm_snapshot' and 'rollback_container_snapshot'. However, it lacks any additional context about the snapshot's purpose or behavior.

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 is provided on when to use this tool versus alternatives such as 'create_backup_job' or when a snapshot should be created. The description does not mention prerequisites, like the container needing to exist or be in a certain state.

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

Deploy Server