Skip to main content
Glama

List Ceph OSDs

proxmox_list_ceph_osds
Read-only

Lists Ceph OSDs with host, up/down and in/out status, device class, usage, PG counts and latency, plus per-host grouping and cluster OSD flags. Filter by host, status or device class.

Instructions

List Ceph OSDs from the OSD tree: host, up/down, in/out, device class, usage, PGs, CRUSH weight, latency and version, plus the per-host grouping and cluster-wide OSD flags (noout etc.). Filter by host, status or device class.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
hostNoOnly OSDs on this host
nodeNoNode to query through (any node with Ceph installed; default PROXMOX_DEFAULT_NODE or the first online node). Results are cluster-wide.
limitNoMaximum number of results (default 1000)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
statusNoOnly OSDs in this state
device_classNoOnly this device class, e.g. hdd, ssd, nvme

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds genuinely useful behavior by disclosing that results include per-host grouping and cluster-wide OSD flags (noout etc.) that are not per-OSD attributes. It does not mention pagination, default limits, or permission needs, which keeps it below a 5.

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?

Two sentences, front-loaded with the resource and return contents, then filtering — no filler. The field enumeration is dense but each item is informative, though 'plus the per-host grouping and cluster-wide OSD flags (noout etc.)' is slightly clunky as an appended clause.

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 and 8 parameters, the description carries the burden of explaining returns and does so thoroughly by listing the returned attributes. Remaining gaps (what raw returns, how limit interacts with paging, node selection fallback) are covered by the schema's own parameter descriptions.

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 88%, so the schema already documents host, status, device_class, node, limit, raw, fields and search. The description only restates the three filter dimensions and adds no syntax, default, or interaction detail beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List Ceph OSDs from the OSD tree') and enumerates exactly what each row carries (host, up/down, in/out, device class, usage, PGs, CRUSH weight, latency, version). It never names a sibling, so the distinction from proxmox_get_ceph_osd (singular detail fetch) is only inferable from the list/get naming rather than stated.

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?

The closing sentence 'Filter by host, status or device class' implies the tool's use case (scanning OSD health/state across the cluster), but there is no explicit when-to-use, no when-not-to-use, and no pointer to proxmox_get_ceph_osd for single-OSD detail or proxmox_get_ceph_crush for topology.

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