Skip to main content
Glama

pve_ceph_mgr_create

Create a Ceph Manager on a Proxmox node. Supports dry-run planning with confirm flag for execution.

Instructions

MUTATION: create a Ceph Manager.

RISK_MEDIUM. mgr_id defaults to the nodename when omitted (named mgr_id, not id, to avoid shadowing the builtin — the wire body/path still uses the schema's literal id, mirroring Wave 6a's cmd-safety id->service_id rename). CAPTURE-or-declare: reads the current manager list before planning (also readable directly via pve_ceph_mgr_list); if unreadable -> complete=False. Dry-run by default (returns a PLAN); confirm=True executes (POST /nodes/{node}/ceph/mgr/{id}) and returns {"status": "submitted", "result": }. No rollback primitive on this plane — revert with pve_ceph_mgr_destroy(mgr_id=...).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node to create the manager on; defaults to the configured node if omitted.
mgr_idNoID for the new manager; defaults to the nodename if omitted.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the create.
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 provided, but the description fully discloses mutation, risk level (RISK_MEDIUM), default behavior for mgr_id, the id rename, dry-run output, and the result format (UPID), compensating entirely for the lack of annotations.

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 detailed and well-structured with labels, but several parenthetical notes make it slightly verbose. Still, every sentence provides value, and it's efficiently front-loaded with key information.

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 that output schema exists, the description covers all essential behavioral aspects: creation, dry-run, risk, defaults, preconditions, and rollback, making it fully adequate for the tool's 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. The description adds meaningful context beyond the schema, such as mgr_id defaulting to nodename, rename from id, and confirm's dry-run effect, elevating it above baseline.

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 explicitly states 'MUTATION: create a Ceph Manager' and distinguishes from related tools like pve_ceph_mgr_list and pve_ceph_mgr_destroy, making the purpose unmistakable.

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?

It clearly explains dry-run vs. confirm=True behavior, mentions prerequisites like reading current manager list, and advises reverting with pve_ceph_mgr_destroy, providing comprehensive when-to-use guidance.

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