Skip to main content
Glama

List storage content

proxmox_list_storage_content
Read-only

Lists Proxmox storage volumes—ISOs, templates, backups, VM/CT disks, snippets, and import files—with format, size, owner VMID, creation time, notes, and protection; filter by content type or VMID.

Instructions

List the volumes on a storage: ISO images, container templates, backups, VM/CT disks, snippets and import files, with format, size, owner VMID, creation time, notes and protection. Filter by content type or VMID (e.g. all backups of guest 100).

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": {
      "storage": "<storage>"
    },
    "name": "proxmox_list_storage_content"
  }
}

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.
vmidNoOnly volumes owned by this guest
limitNoMaximum number of results (default 500)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
contentNoOnly this content type
storageYesStorage ID, e.g. "local" or "local-lvm" (see proxmox_list_storage)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.8/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 safety is covered and the bar is lower. The description still adds real value by documenting the response payload shape (format, size, owner VMID, creation time, notes, protection), which no output schema supplies. It omits the default 500-result cap and the raw/pagination behavior, keeping it below 5.

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 tightly packed sentences: the enumeration of volume types and returned fields comes first, the filtering guidance second. No filler, no restated title, and the scoping information is front-loaded.

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?

With no output schema, describing the returned fields is the key gap the description closes, and it does so well. For an 8-parameter tool it leaves node selection, the default result limit, and the raw/search/fields options entirely to the schema, which is acceptable given 88% coverage but prevents a 5.

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 88%, so the schema already explains node, vmid, limit, search, content, and the raw flag; baseline is 3. The description reinforces only the content and VMID filters and adds no syntax or default details beyond what the schema states.

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+resource ('List the volumes on a storage') and enumerates exactly which volume kinds are covered (ISO images, templates, backups, VM/CT disks, snippets, import files) plus the metadata returned. That is far more specific than the title, but it never names a sibling to distinguish itself from, e.g., proxmox_list_storage or proxmox_list_backup_files, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one concrete usage example ('all backups of guest 100') that shows how to combine the content-type and VMID filters, which is genuinely instructive. However, there is no explicit when-to-use vs. when-not guidance and no alternatives named, so the guidance is implied rather than stated.

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