Skip to main content
Glama

pve_ceph_service_restart

Restart Ceph services on a Proxmox node. Returns a dry-run plan by default; confirm execution to initiate restart with brief I/O interruption.

Instructions

MUTATION: restart Ceph service(s) (systemd unit(s) matching service).

RISK_MEDIUM: brief I/O interruption while the daemon(s) cycle. No CAPTURE — no durable "is this unit currently running" read exists on this plane. Dry-run by default (returns a PLAN); confirm=True executes (POST /nodes/{node}/ceph/restart) and returns {"status": "submitted", "result": }. No rollback primitive on this plane — restart is not revertible.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPVE node to act on; defaults to the configured node if omitted.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the restart.
serviceNoCeph service to restart: '(ceph|mon|mds|osd|mgr)[.<id>]', e.g. 'mon.pve1'. Defaults to 'ceph.target' (the whole stack) if omitted.
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, the description fully covers behavioral aspects: mutation, brief I/O interruption, no durable read, dry-run behavior, confirm execution, and irreversibility. This provides complete transparency.

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 structured with labels like 'MUTATION' and 'RISK_MEDIUM', and is informative without excessive fluff. Could be slightly more concise but remains 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 an output schema exists and description covers all key aspects (purpose, risk, confirm, no rollback), it is contextually complete for an agent to use the tool correctly.

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 coverage is 100%, so baseline is 3. The description adds modest context for the service parameter (e.g., 'ceph.target' default) but does not significantly extend beyond the schema descriptions for node, confirm, and proximo_target.

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 it restarts Ceph service(s) matching a systemd unit, using the verb 'restart' and specifying the resource. This distinguishes it from siblings like start/stop and other Ceph management tools.

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 dry-run by default and confirm flag, risk level, and no rollback, but does not explicitly compare to pve_ceph_service_start or pve_ceph_service_stop to guide when restart is preferred.

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