Skip to main content
Glama

pve_ceph_mds_destroy

Remove a Ceph Metadata Server (MDS) daemon. Dry-run returns a plan; confirm executes the deletion.

Instructions

MUTATION: destroy a Ceph Metadata Server.

RISK_HIGH: any CephFS rank it was actively serving fails over to a standby if one exists, else that filesystem's metadata becomes unavailable. cmd-safety ADVISORY citation (action=destroy, service=mds) is included in the plan's blast_radius — fail-open, never a gate. CAPTURE-or-declare: reads the current MDS list before planning; if unreadable -> complete=False. Dry-run by default (returns a PLAN); confirm=True executes (DELETE /nodes/{node}/ceph/mds/{name}) and returns {"status": "submitted", "result": }. No rollback primitive on this plane — recreate with pve_ceph_mds_create (a NEW daemon, not a byte-for-byte restore).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesID (name) of the MDS to destroy.
nodeNoPVE node the MDS is on; defaults to the configured node if omitted.
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?

No annotations are provided, so the description carries full burden. It explicitly mentions mutation, high risk (RISK_HIGH), failover behavior, cmd-safety advisory, dry-run default, execution path, and irreversibility. This is comprehensive and honest.

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 a single paragraph with clear sections (action, risk, execution flow, recovery). Every sentence adds necessary information without redundancy. Efficient and well-structured.

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 (high-risk mutation, dry-run pattern, no rollback) and presence of output schema, the description covers all critical aspects: risk, failover, execution details, and recovery via a sibling tool. The mention of 'CAPTURE-or-declare' and 'cmd-safety ADVISORY' provides relevant context for the agent.

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 description coverage is 100%, so baseline is 3. The description adds some context for the confirm parameter (dry-run vs execute) but does not significantly enhance understanding beyond the schema. No additional meaning for other parameters.

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's action ('destroy') and resource ('Ceph Metadata Server'). It distinguishes from sibling tools like pve_ceph_mds_create and pve_ceph_mds_list by specifying it is the destruction counterpart, and details the consequences (failover/unavailability).

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 explains when to use the tool (to destroy an MDS) and mentions the alternative pve_ceph_mds_create for recovery. It details the dry-run/confirm pattern and notes no rollback, providing clear usage guidance. However, it does not explicitly list conditions under which the tool should or should not be used.

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