Skip to main content
Glama
tiancode
by tiancode

pve_backup_restore

Destructive

Restore a backup archive to a VM or container ID on a Proxmox node. Overwrite existing guests with force and confirm flags.

Instructions

Restore a backup archive to a VM/CT id. DESTRUCTIVE when overwriting.

    Applies to: vzdump/PBS backup archives (``archive`` is the volid, e.g.
    ``local:backup/vzdump-qemu-100-....vma.zst``); the guest type
    (QEMU vs LXC) is inferred from the archive name. ``node`` is required —
    the target may not exist yet, so it cannot be auto-resolved. ``storage``
    optionally overrides where restored disks are placed.

    Restoring to a NEW (unused) ``vmid`` needs no confirmation. Overwriting
    an EXISTING ``vmid`` destroys that guest's current disks and config:
    it requires ``force=true`` AND ``confirm=true``.

    Waits up to PVE_MCP_TASK_WAIT seconds (restores often run longer — then
    ``task.status`` is "running"; follow the ``upid`` with pve_task_status).
    Returns JSON with ``vmid``/``node``/``type``/``archive`` and ``task``.
    Source: POST /nodes/{node}/qemu (archive=...) or
    POST /nodes/{node}/lxc (ostemplate=..., restore=1).
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeYes
vmidYes
forceNo
archiveYes
confirmNo
storageNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Goes beyond the destructiveHint annotation by detailing conditions for destructiveness: overwriting requires force=true and confirm=true, restoring to new vmid is safe. Also discloses waiting behavior with PVE_MCP_TASK_WAIT and return JSON structure, providing comprehensive behavioral context.

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, front-loaded with the main action, and each sentence adds unique value without redundancy. Appropriate length for the tool's complexity, using paragraphs and formatting effectively.

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

Completeness5/5

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

Given the tool's complexity (6 params, destructive behavior, optional follow-up), the description covers prerequisites, conditions, timeout handling, and return format. Output schema exists (implied), but description already summarizes return fields, ensuring the agent can use it correctly without additional documentation.

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

Parameters4/5

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

With 0% schema description coverage, the description adds meaning for key parameters: explains 'archive' as volid, 'node' as required due to auto-resolution, 'storage' for override, and discusses force/confirm in context. However, node and vmid are not explicitly described beyond being required, and other params like confirm are only implied.

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 tool's action: 'Restore a backup archive to a VM/CT id.' It specifies the types of archives (vzdump/PBS), guest inference from name, and distinguishes itself from sibling tools like pve_backup_create and pve_vm_clone by focusing on restoration from backups.

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

Usage Guidelines5/5

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

Provides explicit when-to-use guidance: applies to specific archive types, node requirement explained, and differentiates between restoring to new vs existing vmid. It also mentions the need for force/confirm when overwriting, and suggests alternative follow-up with pve_task_status for long-running tasks.

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