Skip to main content
Glama
tiancode
by tiancode

pve_snapshot_create

Create a snapshot of a Proxmox VM or container, optionally including RAM state for live snapshots.

Instructions

Create a snapshot of a VM or container.

    Applies to: QEMU VMs and LXC containers, located by ``vmid`` (``node``
    optional and auto-resolved). ``name`` is the snapshot identifier.
    ``vmstate=true`` also saves the RAM state (live snapshot) — QEMU only;
    LXC containers reject it with an error.

    Side effects: creates a snapshot (disk space usage grows over time).
    Waits up to PVE_MCP_TASK_WAIT seconds for the PVE task; returns JSON with
    ``vmid``/``node``/``type``/``snapshot`` and ``task`` (``exitstatus``
    "OK", failure + ``log_tail``, or ``status`` "running" with the ``upid``).
    Source: POST /nodes/{node}/{qemu|lxc}/{vmid}/snapshot.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
nodeNo
vmidYes
vmstateNo
descriptionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations exist, so the description fully discloses behavior: side effects (disk space growth), timeout behavior (waits up to PVE_MCP_TASK_WAIT seconds), return format (JSON with task details), and the underlying REST API endpoint. This is comprehensive.

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?

The description is four sentences, each with a distinct purpose: purpose, applicability, side effects and return, and API source. No fluff, information is front-loaded and well organized.

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?

With an output schema (not shown) and no annotations, the description covers the return format, side effects, and parameter semantics for all but one parameter. It is thorough for a creation tool, though it could mention that snapshots are incremental or discuss retention briefly.

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 0%, so the description adds meaning for 4 of 5 parameters: vmid (locates VM/container), node (optional, auto-resolved), name (snapshot identifier), vmstate (RAM state for QEMU only). It does not explain the 'description' parameter, but the coverage is strong.

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 starts with 'Create a snapshot of a VM or container', a specific verb and resource. It further clarifies applicability to QEMU VMs and LXC containers, distinguishing it from sibling tools like pve_backup_create or pve_snapshot_delete.

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?

It specifies the tool applies to VMs and containers located by vmid, with node optional and auto-resolved. It also notes that vmstate=true is only for QEMU, providing guidance on when to use that parameter. While it does not explicitly contrast with alternative tools, the context 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/tiancode/pve-mcp'

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