Skip to main content
Glama

pbs_node_disk_directory_create

Formats a raw disk and mounts it as a directory datastore on a PBS node. Irreversibly destroys any existing data on the disk.

Instructions

MUTATION: format a disk and mount it as a directory datastore on a PBS node.

RISK_HIGH: FORMATS the named disk immediately — any pre-existing data is destroyed, irreversibly. To see what already exists use pbs_node_disk_directory_list; to remove one use pbs_node_disk_directory_delete (note: PBS's delete has NO cleanup-disks option — it never wipes the disk). Dry-run by default (returns a PLAN); confirm=True executes (POST /nodes/{node}/disks/directory, Smoke-confirm) and returns {"status": "submitted", "result": <task UPID | None>}. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
diskYesBare whole-disk name to format (e.g. 'sda') — NOT a /dev/ path.
nameYesDatastore name to create (3-32 chars, alnum/underscore start).
nodeNoPBS node name (or 'localhost').localhost
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
filesystemNoFilesystem to format with: 'ext4' or 'xfs'. PBS default is ext4 if omitted.
add_datastoreNoIf True, also register a PBS datastore using this directory.
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.
removable_datastoreNoIf True, mark the datastore as removable media.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are present, so the description carries the full burden. It explicitly labels the tool as 'MUTATION' and 'RISK_HIGH', warns about irreversible data destruction, explains dry-run vs confirm results in detail (including raw endpoint and return JSON shape), and clarifies that PBS delete never wipes the disk. This is highly 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 extremely concise (two paragraphs plus a short note on config), with every sentence serving a clear purpose: stating the action, highlighting risk, explaining default behavior, naming alternatives, and detailing output. There is no 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 tool's complexity (8 parameters, output schema, destructive nature), the description adequately covers core behavior, risk, output format, alternatives, and configuration needs. It leverages the schema for parameter details and the output schema for return structure. Minor omission: does not discuss parameter interaction (e.g., filesystem choices), but overall it is fairly complete.

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 description coverage is 100%, so the schema already documents all parameters. The description adds value primarily for the 'confirm' parameter by explaining its effect on execution flow and return type, but does not elaborate on other parameters. Baseline 3 is appropriate as the description complements the schema without being essential.

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 uses a specific verb phrase 'format a disk and mount it as a directory datastore on a PBS node', clearly identifying the resource and action. It distinguishes itself from sibling tools by explicitly naming pbs_node_disk_directory_list and pbs_node_disk_directory_delete, 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?

Provides clear guidance: dry-run default vs confirm execution, mentions alternatives for listing and deletion, and notes config requirement. Does not fully exhaust all possible alternatives (e.g., ZFS disk creation) but covers the most relevant siblings, making usage context quite clear.

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