io.github.AIops-tools/ceph-aiops

mon_status

Read-only

Check which Ceph monitors are in or out of quorum and view the monmap epoch when MON_DOWN or clock-skew warnings appear. Use the target argument to query a specific cluster.

Instructions

[READ] Monitor quorum: mons in/out of quorum and the monmap epoch.

Call this when health flags MON_DOWN or a clock-skew warn — it shows which monitors are actually holding quorum.

Args: target: Ceph target name from config; omit for the default.

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": "mon_status"
  }
}

Input Schema

Name	Required	Description	Default
`target`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 12, 2026

TDQS

A4.2/5.0

Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description reinforces that with a [READ] tag and adds useful trigger context, but discloses nothing further about behavior (e.g., what happens on an unreachable mon, or whether the output changes with quorum state). Adequate but adds limited value beyond the annotation.

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?

Tightly structured: purpose first, then a clear routing condition, then the single argument. Every sentence earns its place with no redundancy.

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 read-only status tool with no output schema, the description adequately sketches the return content (quorum membership and monmap epoch) and covers the sole parameter. Nothing critical is missing, though output format details are absent.

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 0%, so the description carries the burden and does add real meaning: 'target' is a Ceph target name from config, and omitting it uses the default. That resolves the only ambiguity an agent would have, though it gives no format examples.

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?

Names a specific resource (monitor quorum) and states exactly what is returned: mons in/out of quorum plus the monmap epoch. This is clearly distinguishable from siblings like mgr_status, osd_tree, and cluster_health, which cover different subsystems.

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?

Gives an explicit trigger — health flags MON_DOWN or a clock-skew warn — which is exactly the situation where an agent would reach for this tool. It does not name a when-not condition or an alternative tool, so it stops short of a 5.

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