Skip to main content
Glama

List LVM thin pools

proxmox_list_lvm_thin
Read-only

List a node's LVM thin pools with data and metadata usage to monitor metadata space and help prevent storage failures.

Instructions

List a node's LVM thin pools with data and metadata usage. Thin pools that run out of metadata space fail badly, so watch metadata_usage.

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

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

A3.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real domain context beyond that: thin pools fail badly when metadata space runs out, and metadata_usage is the field to watch. It does not cover pagination or output shape, but for a read-only list tool this is solid added value.

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 sentences, no filler, and the core capability is front-loaded before the operational warning. Each sentence earns its place by adding either scope or a concrete monitoring caveat.

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?

There is no output schema, and the description partially compensates by naming the returned metrics (data and metadata usage). However, the undocumented 'fields' and 'search' parameters and the lack of any note on result scope or volume leave gaps an agent would need to resolve by trial.

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?

With only 33% schema description coverage, the description carries a heavier burden, yet it mentions no parameters at all. The node default and proxmox_list_nodes reference live only in the schema, while 'fields' and 'search' are undocumented in both places, leaving two of three parameters semantically unexplained.

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 names a specific verb and resource ("List a node's LVM thin pools") plus the data it returns (data and metadata usage), which distinguishes it from the thick-LVM sibling proxmox_list_lvm. It stops short of explicitly naming that sibling as the non-thin alternative, so it is clear but not fully differentiated.

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: the warning about metadata exhaustion suggests this is a capacity/monitoring call, which is a reasonable when-to-use signal. There is no explicit statement of when to prefer it over proxmox_list_lvm or proxmox_list_disks, and no prerequisites or exclusions are given.

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