Skip to main content
Glama

List physical disks

proxmox_list_disks
Read-only

List a Proxmox node's physical disks with model, size, type, SMART health, and current usage across LVM, ZFS, Ceph, and partitions. Filter to unused disks to find free capacity for new storage.

Instructions

List a node's physical disks with device path, model, serial, size, type (ssd/hdd/nvme/usb), SMART health, wearout and what uses them (LVM, ZFS, Ceph OSD, partitions, mounted). Use type=unused to find disks free for new storage.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
typeNoOnly unused disks, or disks usable as Ceph journal/DB
fieldsNo
searchNo
skip_smartNoSkip SMART health checks (faster)
include_partitionsNoAlso list partitions

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/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 adds value by previewing the returned fields, which matters because there is no output schema, but it omits behavior the agent would want — notably that SMART queries can be slow (only the schema's skip_smart text hints at that) and that results default to PROXMOX_DEFAULT_NODE.

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, zero filler; the payload/field summary comes first and the actionable parameter tip is second. Every clause earns its place and nothing is repeated from the title.

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?

For a seven-parameter read tool with no output schema, the description does the essential work of describing the return shape so an agent can decide whether this call answers its question. Minor gaps remain around node defaulting and the performance cost of SMART, but nothing that would cause a wrong invocation.

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 coverage is 71%, so most parameters are self-documented. The description adds real meaning for the type enum by explaining that type=unused surfaces disks free for new storage, but fields, search, raw, skip_smart, and include_partitions get no elaboration in the description beyond their schema text, so it does not meaningfully exceed the baseline.

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 physical disks') and then enumerates exactly what each entry contains: device path, model, serial, size, type, SMART health, wearout, and consumers (LVM, ZFS, Ceph OSD, partitions, mounted). This makes it clearly distinct from sibling storage tools such as proxmox_list_lvm or proxmox_list_ceph_osds, which report pools rather than hardware.

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?

Gives one concrete, actionable scenario: 'Use type=unused to find disks free for new storage,' which tells an agent exactly when to reach for a specific parameter value. It stops short of naming exclusions or pointing to alternatives (e.g., when to use proxmox_list_lvm instead for pool-level questions), so it is clear context without full routing guidance.

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