Skip to main content
Glama

List Ceph monitors, managers and metadata servers

proxmox_list_ceph_services
Read-only

List Ceph monitors, managers, and metadata servers by type or all, including quorum, active/standby roles, MDS state, host, address, and version to inspect cluster service health.

Instructions

List Ceph daemons of one type or all: monitors (quorum, rank), managers (active/standby) and metadata servers (MDS state, CephFS, rank), with host, address and version.

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_list_ceph_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode to query through (any node with Ceph installed; default PROXMOX_DEFAULT_NODE or the first online node). Results are cluster-wide.
typeNoDaemon type (default all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/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 the safe-read profile is covered. The description adds useful disclosure of what fields come back (host, address, version) and what per-type state is included, but it says nothing about the discrepancy that idempotentHint=false on a plain listing operation, nor about output size or load considerations.

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?

It is a single front-loaded sentence with no filler, and the main action leads. The nested parentheticals make it dense to scan, but every clause carries information about scope or returned fields.

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?

For a two-parameter read-only listing tool with full schema coverage and annotations, the description is nearly sufficient, and by previewing returned fields it partially compensates for the absent output schema. Minor gaps remain around result shape and pagination, but nothing needed to call it correctly is missing.

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%, and the schema already documents both the node and type parameters, including that results are cluster-wide regardless of the node chosen. The phrase 'of one type or all' echoes the type enum but adds no syntax or behavioral detail beyond the schema, so the baseline of 3 applies.

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 and resource ('List Ceph daemons') and enumerates the exact scope: monitors (quorum, rank), managers (active/standby), and metadata servers (MDS state, CephFS, rank). This lets an agent separate it from adjacent Ceph siblings such as the OSD, pool, and CephFS listing tools without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the enumeration of daemon types, so an agent can infer this is the tool for quorum, manager failover, or MDS state checks. However, there is no explicit when-to-use guidance, no statement of when another tool (e.g. get_ceph_status or list_ceph_osds) is the better choice, and no mention of when 'all' versus a specific type is appropriate beyond the schema default.

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