Skip to main content
Glama

pve_ceph_osd_create

Creates a new Ceph OSD by reformatting a block device as BlueStore storage. Dry-run returns a plan; confirm executes the operation with data loss risk.

Instructions

MUTATION: create a new Ceph OSD, consuming and REFORMATTING dev as BlueStore storage.

RISK_HIGH: ALL existing data on dev (and on db_dev/wal_dev, if given) is destroyed. No CAPTURE possible — this is a brand-new OSD, nothing existing to snapshot. Dry-run by default (returns a PLAN); confirm=True executes (POST /nodes/{node}/ceph/osd) and returns {"status": "submitted", "result": } — the NEW OSD's id is NOT in this response, only discoverable afterward via pve_ceph_osd_tree. No rollback primitive on this plane — revert by destroying the new OSD with pve_ceph_osd_destroy once its id is known.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
devYesBlock device to consume as a NEW Ceph OSD (e.g. '/dev/sdb'). ALL existing data on this device is destroyed.
nodeNoPVE node to create the OSD on; defaults to the configured node if omitted.
db_devNoDedicated block device for block.db (RocksDB metadata). Mutually exclusive with osds_per_device.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the create.
wal_devNoDedicated block device for block.wal (write-ahead log). Mutually exclusive with osds_per_device.
encryptedNoEnable OSD encryption (LUKS/dm-crypt). Default False.
db_dev_sizeNoSize in GiB for block.db (>=1). REQUIRES db_dev to also be set.
wal_dev_sizeNoSize in GiB for block.wal (>=0.5). REQUIRES wal_dev to also be set.
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.
osds_per_deviceNoOSD services per physical device (>=1) — for fast NVMe devices only. Mutually exclusive with db_dev/wal_dev.
crush_device_classNoOverride the OSD's CRUSH device class (e.g. 'ssd', 'hdd', 'nvme').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It explicitly notes mutation, data destruction on dev/db_dev/wal_dev, no rollback, dry-run behavior, confirm flag, response format, and how to discover the new OSD ID via pve_ceph_osd_tree. Very comprehensive.

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?

Three sentences packed with essential information. Front-loads mutation and destruction warnings. No wasted words.

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?

Given the tool's complexity (11 params, destructive mutation), the description covers all critical aspects: purpose, risks, execution flow, response format, and recovery path via a sibling tool. The output schema is present but the description complements it with behavioral details.

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% for 11 parameters, and each parameter has a description. The description adds value by explaining the overall flow (dry-run, confirm) and the response structure, which is not in the schema. This goes beyond the baseline of 3.

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?

Explicitly states 'create a new Ceph OSD, consuming and REFORMATTING dev as BlueStore storage.' Clearly indicates the action (create), resource (Ceph OSD), and key constraint (reformatting). Distinct from sibling tools like pve_ceph_osd_destroy and pve_ceph_osd_tree.

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 on when to use (creating new OSD), highlights dry-run default, and explains how to handle failures by destroying the new OSD. Does not explicitly state when not to use, but the warnings about data destruction and the dry-run flow effectively guide the agent.

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