Skip to main content
Glama

List Ceph pools

proxmox_list_ceph_pools
Read-only

Lists Ceph pools with replication size/min_size, PG count and autoscale settings, application, CRUSH rule, and usage percentage to review pool health and capacity.

Instructions

List Ceph pools with replication (size/min_size), PG count and autoscale mode (with the autoscaler's optimal PG count), application, CRUSH rule and usage %. Related: proxmox_get_ceph_pool, proxmox_update_ceph_pool.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode to query through (any node with Ceph installed; default PROXMOX_DEFAULT_NODE or the first online node). Results are cluster-wide.
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.5/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 safety is covered. The description adds that autoscale output includes the autoscaler's optimal PG count, which is real behavioral value, but it says nothing about the query being cluster-wide despite a node parameter, nor about response size when raw is used.

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 compact sentences with the substantive content front-loaded and the alternatives relegated to a trailing 'Related:' clause. The dense field list earns its place because there is no output 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, describing the returned fields is the right compensation and it is done well. Remaining gaps are minor: no note that results are cluster-wide regardless of the node used, and no hint about the cost of raw=true.

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 75% (node, raw, search documented; fields undocumented), so the schema does most of the work. The description mentions no parameter at all, adding no meaning beyond the schema; a 3 is the appropriate baseline here.

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 ('List Ceph pools') immediately scoped to Ceph, with an enumeration of what is reported (size/min_size, PG count, autoscale mode and optimal PG count, application, CRUSH rule, usage %). That distinguishes it from generic storage-pool listing siblings, though it never explicitly says it is not proxmox_list_pools.

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 'Related:' line points at proxmox_get_ceph_pool and proxmox_update_ceph_pool, implying this is the overview/read tool and get is for a single pool, but no when-to-use or when-not-to-use condition is stated. Usage must be inferred from the tool names.

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