Skip to main content
Glama

Get resource pool

proxmox_get_pool
Read-only

Retrieve a Proxmox resource pool's comment and members, including guest status, node, CPU/memory use, and storage usage.

Instructions

Get a resource pool's comment and members: guests (status, node, CPU/memory use) and storage (usage).

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
typeNoOnly members of this type
poolidYesPool ID, e.g. "production" (nested pools as "parent/child"; see proxmox_list_pools)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/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 low-risk read profile is covered. The description adds real value beyond that by spelling out exactly what is returned — comment, guest status/node/CPU-memory figures, and storage usage — which neither the annotations nor the (absent) output schema provide. It does not address permissions or behavior for a nonexistent pool, keeping it off a 5.

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 resource identified first and the returned fields enumerated in compact parentheticals. Nothing is redundant and nothing could be cut without losing content.

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 return-value burden and does so adequately by listing the member kinds and metrics. Combined with fully documented parameters, an agent has enough to call it correctly; only edge cases (nonexistent pool, permission requirements) are unaddressed.

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% and all three parameters are documented in-schema, including the enum for `type` and the nested-pool syntax for `poolid`. The description adds no meaning about `raw`, `type`, or `poolid` filtering beyond what the schema already states, so the 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?

"Get a resource pool's comment and members" names a specific verb and resource and enumerates the payload (guests with status/node/CPU-memory, storage usage). It implicitly separates itself from the storage-pool siblings (proxmox_get_ceph_pool, proxmox_get_zfs_pool) by saying "resource pool," but never explicitly states the distinction, so it stops short of a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative is named. An agent must infer that this is for inspecting one existing pool and that proxmox_list_pools (mentioned only in the schema, not the description) is the way to discover pool IDs.

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