Skip to main content
Glama

pve_ceph_flags_set

Set or unset multiple Ceph cluster flags on Proxmox VE with a single call. Dry-run by default, execute with confirmation to control OSD, scrub, recovery, and I/O behavior.

Instructions

MUTATION: set/unset multiple Ceph cluster flags at once (bulk).

RISK_MEDIUM: flag semantics vary — 'pause' halts ALL client I/O cluster-wide; 'noout'/ 'noscrub'/etc. are routine maintenance toggles. Each flag is TRI-STATE: True sets it, False unsets it, omitted (None, the default for every param) leaves it untouched. CAPTURE-or- declare: reads current flag values before planning (also readable directly via pve_ceph_flags_list/pve_ceph_flag_get); if unreadable -> complete=False. Runs as a worker task (ASYNC, per schema truth) — dry-run by default (returns a PLAN); confirm=True executes (PUT /cluster/ceph/flags) and returns {"status": "ok"|"submitted", "result": <UPID | None>}. No rollback primitive on this plane — revert by re-applying the captured prior values with this same tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
noinNoTrue keeps previously-out OSDs from being marked back in on start; False resumes normal marking; omit to leave untouched.
noupNoTrue prevents OSDs from starting; False allows them to start; omit to leave untouched.
nooutNoTrue stops OSDs from being auto-marked out after the configured interval; False resumes normal marking; omit to leave untouched.
pauseNoTrue PAUSES reads and writes cluster-wide (halts ALL client I/O); False resumes; omit to leave untouched.
nodownNoTrue makes monitors ignore OSD failure reports (won't mark OSDs down); False resumes normal marking; omit to leave untouched.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the change.
noscrubNoTrue disables (light) scrubbing; False re-enables it; omit to leave untouched.
norecoverNoTrue suspends PG recovery; False resumes it; omit to leave untouched.
nobackfillNoTrue suspends PG backfilling; False resumes it; omit to leave untouched.
norebalanceNoTrue suspends PG rebalancing; False resumes it; omit to leave untouched.
notieragentNoTrue suspends cache-tiering activity; False resumes it; omit to leave untouched.
nodeep_scrubNoTrue disables deep scrubbing; False re-enables it; omit to leave untouched.
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 behavioral traits: mutation (MUTATION), risk, tri-state semantics, async worker task (ASYNC), dry-run by default, confirm to execute, return types (plan or status with UPID), and absence of rollback. 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 dense and front-loaded with purpose and risk, but contains necessary detail for complex mutation tool. Slightly verbose but every sentence adds value; no redundancy.

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?

Fully covers purpose, usage, risk, behavioral details (tri-state, async, dry-run, confirm), alternative tools, and no rollback. Since output schema exists, return values need not be detailed. Complete for a mutation tool with this complexity.

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% so baseline is 3. Description adds meta-context beyond schemas: explains tri-state pattern across all flags, confirm parameter's role, and dry-run behavior, enhancing understanding of how parameters interact.

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 'set/unset multiple Ceph cluster flags at once (bulk)', clearly identifying the verb (set/unset), resource (Ceph cluster flags), and bulk nature. Distinguishes from sibling tools like pve_ceph_flag_set (single flag) and pve_ceph_flags_list (read-only).

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 extensive guidance: when to use, risk level (RISK_MEDIUM), specific flag semantics (e.g., 'pause' halts ALL client I/O), alternative tools for reading flags, tri-state behavior, dry-run vs confirm execution, and explicit note about no rollback primitive.

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