Skip to main content
Glama

List ZFS pools

proxmox_list_zfs_pools
Read-only

List a Proxmox node's ZFS pools with size, allocation, fragmentation, dedup ratio and health for quick storage capacity and performance checks.

Instructions

List a node's ZFS pools (zpools) with size, allocation, fragmentation, dedup ratio and health. Use proxmox_get_zfs_pool for the vdev tree and scrub status.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
fieldsNo
searchNo

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?

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing what data the response surfaces (size, allocation, fragmentation, dedup ratio, health). It does not mention result volume, pagination, or that scope is limited to a single node, leaving some behavioral gaps.

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: the purpose and returned metrics come first, the disambiguation second. No filler and no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carrying the returned-field list is appropriate, but a 3-parameter tool with two undocumented parameters leaves the agent guessing how to scope results. Adequate at the purpose level, incomplete at the invocation level.

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

Parameters4/5

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

With only 33% schema coverage, the description must compensate, and it says nothing about the 'fields' or 'search' parameters. The enumerated attributes hint at what 'fields' can select, but 'search' has no explanation anywhere; the 'node' parameter is at least documented in the schema.

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 a node's ZFS pools (zpools)') and enumerates the attributes returned (size, allocation, fragmentation, dedup ratio, health), which separates it cleanly from proxmox_get_zfs_pool's vdev-tree view.

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

Usage Guidelines4/5

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

Explicitly routes the agent to proxmox_get_zfs_pool when the vdev tree or scrub status is needed, giving a clear use/alternative split. It stops short of stating negative conditions such as when not to use this tool at all, so it falls just short of the top score.

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