Skip to main content
Glama

List storage

proxmox_list_storage
Read-only

List Proxmox datacenter storage definitions with type, content, flags, node restrictions, server/path details, and backup retention, merged with per-node live status and usage.

Instructions

List the datacenter's storage definitions (local dirs, LVM, ZFS, NFS, CIFS, PBS, Ceph...) with type, allowed content, shared/enabled flags, node restriction, server/path/pool details and backup retention, merged with each node's live status and usage. Use proxmox_list_storage_content to see what's on one.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoOnly storage available on this node
typeNoOnly storage of this type
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
contentNoOnly storage that allows this content type

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior4/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 real behavioral context beyond that: results are 'merged with each node's live status and usage', which tells the agent this is an aggregated datacenter-plus-node view rather than a flat API passthrough. It does not mention cost, refresh timing, or failure behavior if a node is unreachable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences, front-loaded with the resource and its scope, and the redirect to the sibling is placed last where it acts as a decision cue. The parenthetical backend list overlaps with the type enum in the schema, so a little of the wording is redundant rather than additive.

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?

With six optional parameters, no output schema, and read-only annotations, this description covers what is needed: what the result contains, how it is assembled (definitions merged with per-node status), and which sibling handles the adjacent task. Nothing an agent needs to call it correctly is missing.

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 83%, so descriptions for raw, node, type, search and content already carry the meaning. The description's enumeration of storage types loosely mirrors the type enum but adds no filtering semantics or combination behavior. Baseline 3 is appropriate when the schema does the work.

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?

Specific verb plus resource ('List the datacenter's storage definitions'), and it enumerates the storage backends covered (dir, LVM, ZFS, NFS, CIFS, PBS, Ceph) and the fields returned (type, content, shared/enabled, node restriction, server/path/pool, retention, plus live status/usage). It also explicitly names the sibling it is not ('Use proxmox_list_storage_content to see what's on one').

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 a clear selection rule for the most confusable sibling: use this tool for definitions, proxmox_list_storage_content for contents of a specific storage. It does not address when to prefer proxmox_get_storage or proxmox_get_storage_stats, so the routing is clear but incomplete across all near-neighbors.

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