Skip to main content
Glama

Get volume attributes

proxmox_get_volume
Read-only

Retrieves a Proxmox volume's attributes, including disk path, format, size, used space, notes, and protection flag. Use it to inspect storage volumes by ID.

Instructions

Get a volume's attributes: path on disk, format, size, used space, notes and protection flag.

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": {
      "volume": "<volume>"
    },
    "name": "proxmox_get_volume"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
volumeYesVolume ID, e.g. "local:iso/debian-12.iso" or "local-lvm:vm-100-disk-0" (see proxmox_list_storage_content)
storageNoStorage ID; taken from the volume ID's prefix when omitted

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 the safety profile is covered. The description adds the returned attribute list, which is genuinely useful given there is no output schema, but says nothing about behavior for a missing/invalid volume, permissions needed, or why idempotentHint is false on a read. Useful but thin beyond the annotations.

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 verb and resource first, followed by the attribute list. No filler, no redundancy.

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 tool with full schema coverage, the definition covers the essentials, and the field enumeration partially compensates for the absence of an output schema. However, it omits error behavior for unknown volumes and any note on how returned values (e.g. size vs used space, protection flag) are represented.

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%, so node, volume and storage are all documented in structured data, including the default-node behavior and the storage-prefix fallback. The description adds no parameter meaning of its own, so baseline 3 is correct.

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 (get) and resource (a volume) and enumerates exactly which attributes come back: path, format, size, used space, notes, protection flag. That is concrete enough to separate it from an inventory-style listing tool, but it never names a sibling (e.g. proxmox_list_storage_content) to sharpen the distinction.

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 in the description; it doesn't say whether this is for a single known volume versus enumerating contents. The only routing hints (defaults to PROXMOX_DEFAULT_NODE, 'see proxmox_list_storage_content') live in the schema parameter descriptions, not in the tool description itself.

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