Skip to main content
Glama
tiancode
by tiancode

pve_backup_create

Create a backup of a Proxmox VM or container using vzdump. Specify storage, backup mode, compression, and optional notes. Returns task status for long-running backups.

Instructions

Create a vzdump backup of a VM or container.

    Applies to: QEMU VMs and LXC containers, located by ``vmid`` (``node``
    optional and auto-resolved). ``storage`` is the target backup storage.
    ``mode``: ``snapshot`` (default, no downtime), ``suspend`` (brief
    pause), or ``stop`` (guest is shut down for the backup). ``compress``
    defaults to ``zstd`` (valid: 0, 1, gzip, lzo, zstd). ``notes`` attaches
    a comment to the archive; ``{{...}}`` template variables (e.g.
    ``{{guestname}}``) are expanded by PVE.

    Side effects: creates a backup archive on ``storage``; ``stop`` mode
    shuts the guest down during the backup. Backups often outlast the
    PVE_MCP_TASK_WAIT window — then ``task.status`` is "running" and the
    ``upid`` can be followed with pve_task_status. Returns JSON with
    ``vmid``/``node``/``type``/``storage``/``mode`` and ``task``.
    Source: POST /nodes/{node}/vzdump.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNosnapshot
nodeNo
vmidYes
notesNo
storageYes
compressNozstd

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Without annotations, the description fully carries the burden and discloses side effects: creates backup archive, stop mode shuts guest down. It explains that backups may outlast the task wait window and how to follow up with pve_task_status, along with return JSON structure.

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 front-loaded with the main action and includes necessary details without fluff. However, it could be more structured (e.g., bullet points for parameters) for easier scanning.

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?

Given the tool's complexity (multiple parameters, side effects, long-running tasks), the description covers the key aspects. It explains return JSON fields even without the output schema shown, but could mention potential errors or prerequisites.

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 adds meaning for all parameters: vmid, node, storage, mode (with options), compress (default and valid values), and notes (template variables). This compensates fully.

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 it creates a vzdump backup of a VM or container, specifying the resource (QEMU VMs and LXC containers) and operation. It distinguishes from sibling tools like pve_backup_restore and pve_snapshot_create.

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?

The description provides context for when to use the tool (creating backups) and mentions mode options, but does not explicitly state when not to use it or alternatives. It does offer guidance on handling long-running backups via task status tracking.

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/tiancode/pve-mcp'

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