Skip to main content
Glama

pbs_node_disks_list

List physical disks on a Proxmox Backup Server node, including name, devpath, type, size, status, used, model, serial, and SMART data. Filter by usage type or include partitions.

Instructions

READ-ONLY: list physical disks on a PBS node. Returns name/devpath/disk-type/size/status/ used/model/serial/wwn/wearout/rpm/gpt/partitions per disk. For one disk's SMART detail use pbs_node_disk_smart. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPBS node name (or 'localhost').localhost
skipsmartNoSkip SMART checks (faster, less detail).
usage_typeNoFilter by usage: one of unused, mounted, lvm, zfs, devicemapper, partitions, filesystem.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.
include_partitionsNoAlso include partitions in the result.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided. Description declares 'READ-ONLY', lists return fields, and notes config requirement 'PROXIMO_PBS_*'. Provides useful behavioral context beyond basic 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?

Two concise sentences plus a config note. Front-loaded with 'READ-ONLY: list physical disks'. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists and sibling tools are many, description covers return fields, alternative tool, and config requirement. Complete for a listing tool.

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 100% with good parameter descriptions. Description does not add significant value to parameter meaning beyond listing return fields, which is acceptable 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 'list physical disks on a PBS node' with specific verb and resource, lists return fields, and distinguishes from sibling pbs_node_disk_smart for SMART details.

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?

Explicitly mentions alternative tool 'pbs_node_disk_smart' for SMART details. Declares read-only nature. Does not explicitly state when not to use, but guidance is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server