Skip to main content
Glama

pve_snapshot_create

Create a snapshot restore point for a Proxmox guest. Dry-run by default; set confirm=True to execute.

Instructions

MUTATION: create a snapshot (a restore point). Dry-run by default; confirm=True to execute. Async — returns the task UPID; poll pve_task_status. Needs snapshot-capable storage (ZFS/BTRFS/LVM-thin). To restore to a snapshot use pve_rollback; to remove one use pve_snapshot_delete; to list them use pve_snapshot_list.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoGuest type: `lxc` for a container or `qemu` for a VM.lxc
nodeNoPVE node the guest runs on. Omit to resolve it automatically from the cluster.
vmidYesNumeric ID of the guest — VMID for a QEMU VM or CTID for an LXC container.
confirmNoLeave `false` (default) to get a dry-run PLAN; set `true` to execute the snapshot creation.
snapnameYesName for the new snapshot.
descriptionNoOptional free-text description stored on the snapshot.
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?

With no annotations, description carries full burden. It explicitly labels as 'MUTATION', notes async behavior (returns UPID), and requires snapshot-capable storage. Missing details on idempotency or locks, but key behaviors covered.

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?

Four focused sentences: purpose, dry-run/async, storage requirement, and related tools. No redundancy, effectively front-loaded, every sentence adds value.

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: mutation, async, dry-run, storage prerequisites, and links to sibling tools. With output schema existing, return values not needed. Could mention error scenarios or user permissions, but mostly complete.

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?

Schema has 100% description coverage, so all parameters are already documented. Description adds no new parameter-specific information beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'create a snapshot (a restore point)' with explicit verb and resource. It distinguishes from siblings by naming related tools (pve_rollback, pve_snapshot_delete, pve_snapshot_list) for other operations.

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 mentions dry-run by default with confirm parameter to execute. Provides storage prerequisites and cross-references alternative tools for related actions. Could more explicitly state when not to use, but guidance is clear.

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