Skip to main content
Glama

pve_node_storage_backend_create

Create a storage backend (LVM, LVM-thin, ZFS, or directory) on a Proxmox node. Formats specified disk(s) immediately if confirmed; dry-run by default to review the plan.

Instructions

MUTATION: create a storage backend on the node (lvm/lvmthin/zfs/directory).

Per-backend required params: zfs: devices (comma-sep disk list) + raidlevel lvm/lvmthin: devices (single disk) directory: devices (disk path) + filesystem (e.g. ext4)

RISK_HIGH: FORMATS the named disk(s) immediately — any pre-existing data is destroyed, irreversibly. To see what already exists use pve_node_storage_backend_list; to remove one use pve_node_storage_backend_delete. Dry-run by default (returns a PLAN); confirm=True executes (POST, Smoke-confirm) and returns {"status": "submitted", "result": <task UPID | None>}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kwYes
nameYesName to assign to the new storage backend.
nodeNoPVE node name to create the backend on; defaults to the configured node if omitted.
backendYesStorage backend type to create: one of lvm, lvmthin, zfs, directory.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
devicesNoDisk device(s) consumed by the new backend: comma-separated list for zfs, a single disk path for lvm/lvmthin/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.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, but description fully discloses that it FORMATS disks immediately and irreversibly destroys data. Explains dry-run (PLAN) vs confirm (execution) and return format. No contradictions.

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?

Concise with clear sections: mutation header, per-backend params, risk warning, alternatives, dry-run behavior. Every sentence adds value; no fluff. Front-loaded with purpose.

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 all aspects: purpose, usage, behavior (including risks), parameters, alternatives, and output (PLAN or task UPID). With output schema present, no need to detail return values.

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 high (86%), yet description adds significant value by grouping per-backend required params and clarifying the 'devices' parameter semantics (comma-sep for zfs, single disk for others). Also explains confirm behavior beyond schema.

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: create a storage backend on the node (lvm/lvmthin/zfs/directory)', clearly specifying the action and resource. It also distinguishes from sibling tools by naming pve_node_storage_backend_list and pve_node_storage_backend_delete explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides per-backend required params (zfs, lvm/lvmthin, directory), explains dry-run default and confirm=True execution, and tells when to use alternatives like list or delete. Explicit 'RISK_HIGH' warning about destructive nature.

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