Skip to main content
Glama

pve_restore

Restore a Proxmox guest from a backup archive using a dry-run plan. Confirm to execute, overwriting or creating the guest.

Instructions

MUTATION (DESTRUCTIVE if it overwrites an existing guest): restore a guest from a backup archive. Dry-run by default — the PLAN reads live guest state and states whether it CREATES or OVERWRITES. confirm=True to execute. Async — returns a task UPID. Find the archive's volid first with pve_backup_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoGuest type: lxc or qemu.lxc
nodeNoProxmox node to restore onto; defaults to the configured node if omitted.
poolNoResource pool to place the restored guest in.
vmidYesNumeric ID for the restored guest — new if free, existing to overwrite.
forceNoIf vmid already exists, overwrite/destroy the existing guest instead of failing.
archiveYesVolume ID of the backup archive to restore from.
confirmNoGate: false returns a dry-run PLAN, true executes the restore.
storageYesStorage ID to restore the guest's disks onto (LXC only; ignored for QEMU).
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Reveals mutation, destructive potential, dry-run behavior, async nature, returns task UPID. No annotations provided, so description carries full burden; covers key behavioral aspects without omissions.

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?

Two sentences front-loaded with mutation and destructive warning. Each clause adds necessary information. No redundancy.

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?

Covers essential aspects: restore operation, dry-run mode, execution gate, async result, prerequisite pve_backup_list. Given complexity and output schema existence, description is sufficiently complete.

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?

Schema coverage is 100%, so baseline 3. Description adds extra meaning: archive is volid from pve_backup_list, storage only for LXC, confirm gate, force overwrites. Adds value beyond schema.

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?

Clearly states it restores a guest from a backup archive. Differentiates mutation and potential destruction, distinguishes from sibling pve_backup_list (finding archive) and pve_backup (creating backups).

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?

Explicitly says dry-run by default, confirm=True to execute. Advises to find archive with pve_backup_list. Lacks explicit comparison to pve_clone or pve_rollback, but context is clear enough.

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/john-broadway/proximo'

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