Skip to main content
Glama

Get ZFS pool status

proxmox_get_zfs_pool
Read-only

Retrieve detailed ZFS pool status—state, scrub/resilver results, errors, and vdev tree with read/write/checksum counters—to diagnose pool health on a Proxmox node.

Instructions

Get a zpool's detailed status (like zpool status): state, status/action messages, last scrub/resilver, errors and the vdev tree with read/write/checksum error counters.

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

Input Schema

NameRequiredDescriptionDefault
nameYesPool name, e.g. "rpool"
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.

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 carried by structured data. The description adds real value beyond that by spelling out the payload shape (state, status/action messages, scrub/resilver history, error counters, vdev tree), which serves as a de facto output contract given no output schema exists. It does not mention behavior on a missing pool or the odd idempotentHint=false, so it is not exhaustive.

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 dense sentence that front-loads the verb and resource, then the payload fields, with no filler. Every clause earns its place by naming something the caller will actually receive.

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 correctly compensates by enumerating the returned data, and the schema fully documents both parameters. What is missing is minor for a read-only diagnostic tool: error behavior for an unknown pool name and any pagination or size caveats on the vdev tree.

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 the schema already explains that `name` is the pool (e.g. "rpool") and that `node` defaults to PROXMOX_DEFAULT_NODE with a pointer to proxmox_list_nodes. The description adds no parameter meaning on top of that, which is the correct baseline of 3 when the schema does the work.

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?

The description gives a specific verb and resource ("Get a zpool's detailed status") and anchors it with the well-known `zpool status` analog, then enumerates the fields returned. It implicitly differentiates itself from proxmox_list_zfs_pools via the word "detailed," but never names a sibling or states the list-vs-detail split explicitly, 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 Guidelines3/5

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

Usage is only implied: an agent can infer this is the deep-dive call versus a list call, but the description never says when to reach for it, when not to, or which sibling to use for a simpler pool inventory. No prerequisites, no exclusions, no named alternative.

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