Skip to main content
Glama

pve_node_disk_wipe

Wipes all data and partition table from a node disk irreversibly. Dry-run returns a plan; confirm to execute.

Instructions

MUTATION: wipe ALL data and the partition table on a node disk.

RISK_HIGH, NO UNDO: DESTROYS all data, partitions, and filesystems on the named disk — more destructive than pve_node_disk_initgpt, which only overwrites the partition table. Dry-run by default (returns a PLAN); confirm=True executes (PUT /disks/wipedisk, Smoke-confirm) and returns {"status": "submitted", "result": <task UPID | None>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diskYesDevice path/identifier of the disk to wipe (e.g. /dev/sda); ALL data and the partition table are destroyed.
nodeNoPVE node name the disk lives on; defaults to the configured node if omitted.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the irreversible wipe.
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 provided, the description carries the full burden. It explicitly labels the tool as MUTATION, RISK_HIGH, and NO UNDO, and details the dry-run vs execution modes including the HTTP endpoint and response format.

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 concise with two focused paragraphs. The first states purpose and risk, the second explains the two modes of operation. No unnecessary information.

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?

Given the tool's destructive nature and the presence of an output schema, the description covers the key behavioral aspects: dry-run, execution, risk, and response format. It does not cover error handling or partial failures, but is sufficient for an AI agent to use correctly.

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?

The input schema already describes all 4 parameters with 100% coverage. The description adds value by explaining the default behavior of confirm (false = dry-run) and the return formats for both modes, which goes beyond the schema descriptions.

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 verb 'wipe', the resource 'node disk', and the scope 'ALL data and the partition table'. It also distinguishes itself from the sibling tool pve_node_disk_initgpt by noting it is more destructive.

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?

The description explains the dry-run default behavior and when to use confirm=True. It provides a warning about high risk and no undo, but does not explicitly list alternative tools for less destructive actions.

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