List storage resources across the entire Proxmox cluster or for a specific node, providing quick visibility into available storage for inspection and management.
List storage globally or for a node.
| Name | Required | Description | Default |
|---|---|---|---|
| node | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. 'List' implies a read-only operation and the global-or-node scoping is a useful behavioral distinction, but no further behavior is disclosed beyond that scope.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is one short sentence with no filler. It front-loads the operation and immediately communicates the key scoping choice.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter list tool with an output schema, the description covers the essential invocation modes. However, it does not address when to prefer this over sibling tools or any special behaviors, leaving some context gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must clarify the node parameter. 'Globally or for a node' effectively conveys that omitting node gives global scope and supplying it restricts to a node, though it does not name the parameter or describe its format.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource: 'List storage', and adds the global-versus-node scoping that distinguishes it from sibling list tools like pve_list_vms and pve_list_resources. It is immediately clear what the tool operates on.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool versus alternatives such as pve_list_resources or pve_list_nodes. The description states the operation but does not mention exclusions, prerequisites, or sibling routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.