Skip to main content
Glama

pdm_pve_qemu_snapshot_delete

Delete a named QEMU snapshot from a VM on a PDM-registered Proxmox remote. Dry-run by default; use confirm=True to permanently remove the snapshot's saved state.

Instructions

MUTATION: delete a named VM snapshot on a PDM-registered remote, through PDM.

Removes only the snapshot's saved state, not the VM. Irreversible — there is no UNDO. For a container snapshot use pdm_pve_lxc_snapshot_delete; to create rather than delete a snapshot use pdm_pve_qemu_snapshot_create. Dry-run by default (returns a PLAN); confirm=True executes and returns a PDM task reference (track with pdm_tasks_list; pve_task_status cannot poll a PDM UPID).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vmidYesNumeric VMID of the target VM, as a string.
remoteYesPDM-registered remote (Proxmox cluster) hosting the VM.
confirmNoFalse (default) returns a PLAN only; True deletes it.
snapnameYesName of the snapshot to delete.
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
Behavior5/5

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

Given no annotations, the description discloses irreversibility ('no UNDO'), limited scope (removes state only, not VM), dry-run default, execution behavior, and task tracking limitations. This is comprehensive for a mutation tool.

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 plus a brief note. Front-loaded with MUTATION label and core action. No wasted words; 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 purpose, alternatives, irreversible nature, dry-run/confirm, and task tracking. Lacks explicit error handling or prerequisites, but overall sufficient for a mutation tool with an output schema.

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 coverage is 100%, so description adds little extra meaning beyond parameter names and types. The dry-run/confirm behavior is explained, but it overlaps with the schema's confirm parameter description.

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 action: 'delete a named VM snapshot on a PDM-registered remote, through PDM.' It distinguishes from siblings by referencing the container counterpart and the create tool.

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?

Provides explicit when-to-use via siblings and describes the dry-run/confirm workflow. Lacks explicit prerequisites (e.g., snapshot must exist), but alternatives and tracking guidance are strong.

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