Skip to main content
Glama

pve_ceph_osd_out

Exclude a Ceph OSD from the CRUSH acting set by marking it out, initiating data rebalance away from the OSD. Supports dry-run planning before execution.

Instructions

MUTATION: mark a Ceph OSD 'out' — excluded from the CRUSH acting set; triggers data rebalance/recovery AWAY from it.

RISK_MEDIUM. No upstream cmd-safety check exists for the 'out' action (cmd-safety's action enum is {stop, destroy} only — 'out' neither stops the daemon nor destroys anything). CAPTURE-or-declare: reads the OSD CRUSH tree before planning; if unreadable -> complete=False. Runs SYNCHRONOUSLY (schema: returns null) — dry-run by default (returns a PLAN); confirm=True executes (POST /nodes/{node}/ceph/osd/{osdid}/out) and returns {"status": "ok", "result": None}. No rollback primitive on this plane — revert with pve_ceph_osd_in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node the OSD is on; defaults to the configured node if omitted.
osdidYesOSD ID to mark out (0 is a valid id).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the change.
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?

With no annotations, description fully discloses risk level (RISK_MEDIUM), side effects (data rebalance/recovery), execution mode (synchronous), dry-run behavior, lack of rollback, and dependency on CRUSH tree readability. 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured and front-loaded but slightly verbose. Every sentence adds value, but could be more concise without losing clarity. Overall effective.

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 (mutation with side effects, dry-run, synchronous execution), the description covers risk, behavior, parameters, error handling, and revert path. Output schema exists, so return values are documented. Fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds meaning: explains confirm parameter (false=plan, true=execution), OSD ID validity, node default, and proximo_target usage. Adds value 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?

The description clearly states the tool marks a Ceph OSD as 'out', excluding it from the CRUSH acting set and triggering data rebalance/recovery. This specific verb+resource distinguishes it from siblings like pve_ceph_osd_in and pve_ceph_osd_destroy.

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 explicit guidance: dry-run by default, confirm=True executes, no upstream cmd-safety check, reversion via pve_ceph_osd_in, and synchronous execution. Tells when to use (marking OSD out) and when not (revert with another tool).

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