Skip to main content
Glama

Get Ceph status

proxmox_get_ceph_status
Read-only

Get summarized Ceph cluster health via Proxmox: overall status, monitor quorum, manager roles, OSD counts, PG states, usage and client I/O. Start here before drilling into pools or services.

Instructions

Summarized Ceph cluster health: HEALTH_OK/WARN/ERR with each health check, monitor quorum, active/standby managers, OSD counts (up/in/down), PG states, raw usage and client I/O. Start here for any Ceph question; drill down with proxmox_list_ceph_osds, proxmox_list_ceph_pools or proxmox_list_ceph_services.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_get_ceph_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode to query through (any node with Ceph installed; default PROXMOX_DEFAULT_NODE or the first online node). Results are cluster-wide.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered structurally; the description adds useful disclosure of what data the summary surfaces, which goes beyond the annotation set. It says nothing about permissions needed for Ceph visibility, response size when the cluster is degraded, or freshness of the data, and the 'raw' flag's cost is only handled in the schema. Adequate but short of rich behavioral context.

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?

Two sentences, zero filler: the first front-loads what the payload contains, the second front-loads the routing instruction. Every clause earns its place and the entry-point advice comes after the content description in the correct order of reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly takes on the burden of describing the return shape by enumerating health checks, quorum, managers, OSD counts, PG states, usage and I/O. Combined with the routing guidance, an agent has nearly everything needed; only the effect of the 'raw' flag on that return shape is left unaddressed.

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 description coverage is 100%, so both the 'raw' and 'node' parameters already carry clear meaning, and the baseline is 3. The description adds one meaningful clarification beyond the schema by implying the result is a consolidated summary rather than per-node data, complementing the schema's note that results are cluster-wide. It does not, however, explain when to set raw=true, which leaves a small gap.

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 names a specific verb+resource (summarized Ceph cluster health) and then enumerates exactly what the summary contains: health checks, monitor quorum, manager roles, OSD counts, PG states, raw usage and client I/O. That level of specificity distinguishes it from siblings such as proxmox_get_ceph_osd or proxmox_get_ceph_pool without needing to open any schema.

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 gives an explicit entry-point rule ("Start here for any Ceph question") and names the concrete alternatives to use for drill-down (proxmox_list_ceph_osds, proxmox_list_ceph_pools, proxmox_list_ceph_services). The when-to-use and when-to-switch guidance is fully spelled out rather than implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools