Skip to main content
Glama

pbs_node_disk_initgpt

Initialize a GPT partition table on a whole PBS disk. Dry-run returns a plan; confirm executes the irreversible operation.

Instructions

MUTATION: initialize a GPT partition table on a whole PBS disk.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diskYesBare WHOLE-disk name to initialize with a new GPT partition table (e.g. 'sda', 'nvme0n1') — NOT a /dev/ path and NOT a partition; overwrites the existing partition table.
nodeNoPBS node name (or 'localhost').localhost
uuidNoOptional UUID to assign to the new GPT table.
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
Behavior4/5

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

No annotations are present, so the description carries full weight. It clearly labels the tool as MUTATION, states RISK_HIGH, and notes irreversibility. It also describes the dry-run safety mechanism and the execution result. The config requirement 'Needs PROXIMO_PBS_* config' adds context, though it could mention more about authentication or error states.

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?

The description is concise and front-loaded with the purpose and risk. It packs essential information (action, risk, comparison, behavior, response, config) into a single paragraph without unnecessary words. Could be slightly more structured for scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the core functionality, risk, and execution flow. However, it omits details about the dry-run output ('PLAN' structure) and does not specify prerequisites or error conditions. Given the tool's complexity and the presence of an output schema, these gaps are noticeable.

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 100% with detailed parameter descriptions. The description adds value by explaining the effect of the confirm parameter (dry-run vs. execution) and the overall behavior, which goes beyond the schema's structural definitions.

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?

Description starts with 'MUTATION: initialize a GPT partition table on a whole PBS disk,' providing a specific verb and resource. It also differentiates from the sibling tool pbs_node_disk_wipe by noting it is less destructive, clarifying its unique scope.

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 confirm=True execution, including the HTTP endpoint and response format. It contrasts with pbs_node_disk_wipe to guide tool selection, but does not explicitly state when NOT to use this tool or list all alternative scenarios.

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