Skip to main content
Glama

List LVM volume groups

proxmox_list_lvm
Read-only

List a node's LVM volume groups with size, free space, and physical volumes to inspect storage capacity and allocation.

Instructions

List a node's LVM volume groups with size, free space and physical volumes.

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

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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description usefully adds what the response contains (size, free space, physical volumes) in the absence of an output schema, but says nothing about whether results are node-scoped only, whether storage must be LVM-backed, or why idempotentHint is false for a read.

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 scope (node) first and the returned data second; nothing is padded or repeated from 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?

For a simple read-only list tool the purpose and return shape are adequately covered, and annotations carry the safety profile. However, with two of three parameters undocumented and no output schema, an agent still cannot tell how to shape or filter results, which is a real gap.

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 description coverage is only 33%: node is documented in the schema, but 'fields' and 'search' are bare typed properties with no explanation anywhere. The description's phrase 'with size, free space and physical volumes' hints at selectable output fields but never explains that 'fields' filters them or what 'search' matches, so it fails to compensate for the coverage gap.

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?

States a specific verb and resource ('List a node's LVM volume groups') plus the returned attributes (size, free space, physical volumes), so an agent knows exactly what the tool retrieves. It does not distinguish itself from the sibling proxmox_list_lvm_thin, which is the obvious confusion risk in this namespace, keeping it below 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?

The listing intent is clear and read-only, giving implied usage, but there is no explicit when-to-use guidance and no mention of when to prefer proxmox_list_lvm_thin or proxmox_list_disks instead. The defaulting behavior for node lives in the schema, not the description.

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