Skip to main content
Glama

Get Ceph pool

proxmox_get_ceph_pool
Read-only

Retrieve a Ceph pool's settings, including size, PG count, CRUSH rule, and flags, plus optional usage and I/O statistics to monitor capacity and performance.

Instructions

Get one Ceph pool's settings (size, min_size, PGs, autoscaler, CRUSH rule, application, protection flags) and, with statistics=true, its usage and I/O statistics.

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": {
      "name": "<name>"
    },
    "name": "proxmox_get_ceph_pool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesPool name
nodeNoNode to query through (any node with Ceph installed; default PROXMOX_DEFAULT_NODE or the first online node). Results are cluster-wide.
statisticsNoInclude usage and I/O statistics (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/5.0
Behavior4/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 real value by disclosing the returned field set and that the response content changes based on statistics. It does not address the idempotentHint=false flag or error behavior, but for a read-only getter the added return-shape context is meaningful.

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 front-loaded sentence with the primary action first and the conditional modifier second. The parenthetical field list is dense but every item is informative and nothing is redundant filler.

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 compensates well by enumerating the returned settings and the statistics payload. What remains thin is failure behavior (invalid pool name, node without Ceph) and explicit routing versus the list tool, which a read-only getter could reasonably cover in one more clause.

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%, so the schema already documents name, node, and statistics (including the cluster-wide semantics of node). The description only lightly reinforces the statistics flag ('with statistics=true, its usage and I/O statistics') and adds no format or default nuance beyond the schema, so 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?

Specific verb+resource ('Get one Ceph pool's settings') with an enumerated field list (size, min_size, PGs, autoscaler, CRUSH rule, application, protection flags) that makes the payload unambiguous. It does not explicitly name the sibling it complements (proxmox_list_ceph_pools) to say 'use that to enumerate, this to inspect one', so sibling differentiation is only implied by 'one'.

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 'Get one Ceph pool' and there is a concrete invocation hint ('with statistics=true, ...'), which tells the agent how to widen scope. However there is no explicit when-to-use vs. proxmox_list_ceph_pools, no guidance on whether statistics is expensive, and no note on what happens for a nonexistent pool name.

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