Skip to main content
Glama

pve_ceph_init

Initialize default Ceph configuration on a Proxmox node. Dry-run returns a plan; confirm=True executes the setup.

Instructions

MUTATION: create the initial Ceph default configuration and set up symlinks on a node.

RISK_MEDIUM: one-time cluster-bootstrap step. IDEMPOTENT on re-call (schema truth): if a [global] section already exists in ceph.conf, the existing fsid/auth/pool defaults are preserved and most parameters here are silently ignored — this is NOT guaranteed to apply the options above on a re-call. No CAPTURE possible — no 'current Ceph init state' read exists; idempotent re-call is itself the safety net. Dry-run by default (returns a PLAN); confirm=True executes (POST /nodes/{node}/ceph/init) and returns {"status": "ok"| "submitted", "result": None}. No rollback primitive on this plane.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node to initialize; defaults to the configured node if omitted.
sizeNoTargeted number of replicas per object (1-7, default 3).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the init.
networkNoNetwork (CIDR) to use for all Ceph-related traffic.
pg_bitsNoPlacement-group bits (6-14, default 6). Deprecated in recent Ceph versions.
min_sizeNoMinimum number of available replicas per object to allow I/O (1-7, default 2).
disable_cephxNoDisable cephx authentication. WARNING: cephx protects against man-in-the-middle attacks; only consider disabling on a private network.
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.
cluster_networkNoSeparate cluster network (CIDR) for OSD heartbeat/replication/recovery traffic; REQUIRES network to also be set.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description fully discloses behavior: it is a mutation (RISK_MEDIUM), one-time step, idempotent on re-call (with caveat about silent ignore), supports dry-run by default, returns a PLAN or status on confirm, and states no rollback primitive exists. This is comprehensive.

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 relatively long but each sentence adds value: purpose, risk, idempotency, dry-run, output, and limitations. It is well-structured with front-loaded key information. Minor redundancy (e.g., repeating 'two sentences' could be slightly tighter, but overall efficient.

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 complexity of Ceph initialization, the description covers all essential aspects: purpose, risk, idempotency, dry-run behavior (including confirm parameter), return values (PLAN or status), and no rollback. The input schema fully documents parameters, and an output schema exists (per context signals). No gaps identified.

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 the description does not need to repeat parameter details. It adds context for the 'confirm' parameter (dry-run vs execute) but does not elaborate on other parameters beyond what the schema provides. 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 it creates the initial Ceph configuration and sets up symlinks on a node, specifying a precise verb and resource. It distinguishes this tool from sibling Ceph tools (e.g., pve_ceph_mon_create) by labeling it as a one-time cluster-bootstrap step.

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 explicitly marks this as a 'one-time cluster-bootstrap step' and explains dry-run behavior and idempotency on re-call. It provides clear guidance on when to use (initialization) and how to use (confirm parameter), though it does not explicitly mention when not to use or suggest alternative tools.

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