Skip to main content
Glama

Get Ceph OSD details

proxmox_get_ceph_osd
Read-only

Retrieves one Ceph OSD's daemon metadata and logical volume details, including devices, BlueStore, memory, version, and block/DB/WAL mappings, to inspect and troubleshoot cluster storage.

Instructions

Get one OSD's details: daemon metadata (devices, BlueStore, memory, version) and its logical volume info (block/DB/WAL devices).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "osdid": "<osdid>"
    },
    "name": "proxmox_get_ceph_osd"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode hosting the OSD (looked up from the OSD tree when omitted)
osdidYesOSD ID number, e.g. 3 for osd.3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/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 description does not need to re-establish read safety. It adds useful content — that both daemon metadata and LV topology are returned in one call — but says nothing about behavior when the OSD ID does not exist, whether the node lookup can fail, or how costly the call is. (The idempotentHint=false annotation is odd for a pure read but is not contradicted by anything in the text.)

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?

A single sentence, front-loaded with the core action and then the payload breakdown via a colon. No filler, no restatement of the title, and the parenthetical detail is genuinely informative.

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 carries the burden of describing return values, and it does so at a useful level (daemon metadata fields plus block/DB/WAL devices). Minor gaps remain around failure modes for an unknown OSD ID and whether the implicit node resolution affects results, but nothing essential for invoking 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 coverage is 100%: the schema already explains osdid ("OSD ID number, e.g. 3 for osd.3") and node ("looked up from the OSD tree when omitted"). The description adds no parameter-level meaning beyond that, which is the baseline expectation when the schema does the heavy lifting.

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 ("Get one OSD's details") and enumerates the returned content (daemon metadata: devices, BlueStore, memory, version; logical volume info: block/DB/WAL). This distinguishes it from the sibling list_ceph_osds by scope (single OSD vs. enumeration), though the description never names that sibling explicitly.

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 only implied by the singular scope ("one OSD's details") — an agent can infer this is the detail lookup after finding an ID via proxmox_list_ceph_osds, but nothing states that. No when-not-to-use or prerequisite guidance is present.

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