Skip to main content
Glama

List resource pools

proxmox_list_pools
Read-only

Lists Proxmox resource pools with their comments and member counts so you can review permission groups and organization. Supports search filtering by name, ID, or tags.

Instructions

List resource pools (groups of VMs, containers and storage used for permissions and organisation) with their comments and member counts. Not ZFS or Ceph pools; see proxmox_get_pool for members.

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

Input Schema

NameRequiredDescriptionDefault
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

A4.3/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 that results carry comments and member counts, which is genuinely useful given there is no output schema. It does not mention result sizing or whether filtering happens server-side, which would have completed the picture.

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?

Two tight sentences with no filler. The core purpose and scope come first, the sibling disambiguation second, so it is front-loaded and every clause earns its place.

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?

For a two-parameter read-only list tool with no output schema, the description supplies the return content (comments, member counts) and the domain boundary, which is most of what an agent needs. The only real gap is the undisclosed 'fields' projection parameter, which matters for a listing endpoint.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: the 'search' parameter is documented in the schema, but 'fields' has no description anywhere. The description never mentions either parameter, so it does not compensate for the undocumented 'fields' array or clarify what field names it accepts.

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

Purpose5/5

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

States a specific verb and resource ('List resource pools') and immediately defines what a pool is here ('groups of VMs, containers and storage used for permissions and organisation'). It also explicitly disambiguates from the three similarly-named siblings (ZFS pools, Ceph pools) and from proxmox_get_pool, so an agent can pick correctly without opening a schema.

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

Usage Guidelines5/5

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

Gives explicit exclusions ('Not ZFS or Ceph pools') that map cleanly onto the proxmox_list_zfs_pools and proxmox_list_ceph_pools siblings, and routes the agent to proxmox_get_pool when members rather than counts are needed. Both when-to-use and when-not-to-use are covered.

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