Skip to main content
Glama
tiancode

pve-mcp

by tiancode
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

pve_vm_delete

Destructive

Delete a Proxmox VM or container permanently. Requires confirm=true to destroy the guest and disks irreversibly, with optional purge from jobs and HA.

Instructions

Delete a VM or container permanently. DESTRUCTIVE.

    Applies to: QEMU VMs and LXC containers, located by ``vmid`` (``node``
    optional and auto-resolved). Requires ``confirm=true``: the guest and
    ALL of its disks are destroyed irreversibly (backups on backup storage
    are kept). ``purge=true`` additionally removes the vmid from backup
    jobs, replication and HA configuration.

    Side effects: permanently destroys the guest. The guest must be stopped
    first (PVE rejects deleting a running guest). Waits up to
    PVE_MCP_TASK_WAIT seconds; returns JSON with the deleted ``vmid``/
    ``node``/``type`` and ``task``.
    Source: DELETE /nodes/{node}/{qemu|lxc}/{vmid}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNo
vmidYes
purgeNo
confirmNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description elaborates on permanent destruction, irreversibility, side effects, and task waiting behavior. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections and front-loaded purpose. Slightly verbose but every sentence adds value.

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?

Covers prerequisites, parameters, side effects, blocking behavior, return value, and source endpoint. Complete for a destructive tool with output schema.

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

Parameters5/5

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

Adds meaning to all four parameters: explains vmid identification, node auto-resolution, confirm requirement, and purge effects. Schema has no parameter descriptions, so the description fully compensates.

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 deletes a VM or container permanently, using specific verbs and resources. It is distinctly different from sibling tools like pve_vm_clone or pve_vm_power.

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 prerequisites (guest must be stopped), required parameter (confirm=true), and additional option (purge). However, it does not explicitly mention alternative tools for non-destructive removal.

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