Skip to main content
Glama

Get Ceph CRUSH map and rules

proxmox_get_ceph_crush
Read-only

Retrieve a Ceph CRUSH map's devices, buckets, and rules, plus rule names usable as a pool's crush_rule, to inspect cluster placement and choose pool rules.

Instructions

Get the decompiled CRUSH map (devices, buckets, rules) and the list of CRUSH rule names usable as a pool's crush_rule.

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

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.
rules_onlyNoOnly list the rule names (much shorter)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.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 the safety profile is covered. The description adds the meaningful detail that the map is 'decompiled' (raw CRUSH text parsed into structure) and that returned rule names are those valid for pool configuration, but it says nothing about output size, cost, or why idempotentHint is false for a read.

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 with zero filler, front-loading the primary return value and then the secondary rule-name list. Every clause earns its place and nothing is repeated from the title or schema.

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 does the work of naming the three top-level sections an agent will receive plus the rule-name variant, which is adequate for a read-only two-parameter tool. It could go further on the shape/size of the decompiled map, but nothing needed to call the tool 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%, so both node and rules_only are already documented with adequate descriptions, including the cluster-wide caveat. The description's only added meaning is the pool-configuration purpose of the rule names; it does not elaborate on the short-form mode. Baseline 3 applies when the schema carries the parameters.

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?

The description names a specific verb and resource ('Get the decompiled CRUSH map') and enumerates its contents (devices, buckets, rules) plus the rule-name list, which clearly separates it from sibling Ceph getters like proxmox_get_ceph_pool or proxmox_get_ceph_osd. It does not explicitly name a sibling it is not, so it stops short of the 5 tier.

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

Usage Guidelines2/5

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

The clause 'usable as a pool's crush_rule' hints at why an agent would want the rule list, but there is no explicit when-to-use, when-not-to-use, or alternative named among the many Ceph siblings. The agent must infer the scenario from the resource name alone.

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