Skip to main content
Glama

pve_node_disk_initgpt

Initialize a new GPT partition table on a disk, overwriting the existing table. Use dry-run mode to review changes before irreversible execution.

Instructions

MUTATION: initialize a GPT partition table on a node disk.

RISK_HIGH: overwrites the existing partition table on the named disk; irreversible — less destructive than pve_node_disk_wipe, which also erases the underlying data. Dry-run by default (returns a PLAN); confirm=True executes (POST /disks/initgpt, Smoke-confirm) and returns {"status": "submitted", "result": <task UPID | None>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diskYesDevice path/identifier of the disk to initialize with a new GPT partition table (e.g. /dev/sda); overwrites the existing partition table.
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 GPT init.
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?

With no annotations, the description fully carries the burden. It discloses it's a MUTATION, RISK_HIGH, irreversible, and overwrites the partition table. It explains the default dry-run returns a PLAN and confirm=true returns a submission status with UPID. This is comprehensive and transparent.

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, front-loaded with key labels (MUTATION, RISK_HIGH), and structured in a few sentences. Every sentence provides essential information without redundancy or fluff.

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 existence of an output schema, the description appropriately covers behavior, risk, sibling comparison, and default vs confirm execution. It misses minor details like disk validation or error scenarios, but overall it is sufficient for safe usage.

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 beyond schema. The only added value is clarifying the confirm parameter's dry-run vs execute behavior. The disk parameter is already described in the schema, so no extra depth. 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?

The description clearly states the tool initializes a GPT partition table on a node disk, using a specific verb and resource. It distinguishes itself from the related sibling pve_node_disk_wipe by noting it's less destructive, making the purpose unambiguous.

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 vs confirm behavior and contrasts with a more destructive sibling tool. However, it lacks explicit guidance on prerequisites (e.g., disk must be unmounted) or when not to use beyond wipe comparison, leaving some decision support gaps.

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