Skip to main content
Glama

pve_ceph_mgr_destroy

Destroy a Ceph Manager on a Proxmox node. Dry-run returns a plan; set confirm=true to execute. Without a standby, cluster monitoring and orchestration become unavailable until a new manager is created.

Instructions

MUTATION: destroy a Ceph Manager.

RISK_HIGH: if this was the ACTIVE manager, a standby (if any) takes over; with none, cluster monitoring/orchestration modules go dark until a manager is recreated. NO cmd-safety citation — cmd-safety's service enum is {osd, mon, mds}; mgr was never in it (the plan states this plainly rather than inventing a check). CAPTURE-or-declare: reads the current manager list before planning; if unreadable -> complete=False. Dry-run by default (returns a PLAN); confirm=True executes (DELETE /nodes/{node}/ceph/mgr/{id}) and returns {"status": "submitted", "result": }. No rollback primitive on this plane — recreate with pve_ceph_mgr_create (a NEW manager, not a byte-for-byte restore).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node the manager is on; defaults to the configured node if omitted.
mgr_idYesID of the manager to destroy.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the destroy.
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?

Since no annotations are provided, the description carries full burden. It discloses risk high if active manager, behavior of standby failover, no cmd-safety citation, capture-or-declare step, dry-run vs execution, and absence of rollback. This is comprehensive beyond what annotations would typically provide.

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?

The description is concise (around 150 words), well-structured with clear labels (MUTATION, RISK_HIGH, etc.), and front-loads critical information. Every sentence adds value without unnecessary repetition.

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 no annotations and no output schema in the context, the description covers purpose, risk, behavior, dry-run semantics, execution details, rollback absence, and relation to create tool. It leaves little ambiguity for the agent to misuse the tool.

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% with clear parameter descriptions. The description adds value by explaining that confirm=False returns a PLAN and confirm=True executes via DELETE endpoint, providing context beyond the schema defaults. This exceeds 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?

The description starts with 'MUTATION: destroy a Ceph Manager,' which clearly states the action and resource. It distinguishes from siblings like pve_ceph_mgr_create and pve_ceph_mgr_list by explaining the behavior of destroying a manager and mentioning the alternative tool for recreation.

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?

The description provides explicit guidance: it explains that dry-run is default and confirm=True is needed to execute, mentions no rollback and suggests recreating with pve_ceph_mgr_create, and describes prerequisites like reading the current manager list. This helps the agent decide when to use this tool and what to expect.

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