Skip to main content
Glama

Get storage

proxmox_get_storage
Read-only

Retrieve a Proxmox storage definition and its status and usage across nodes. Pass a node to get detailed status there, including active state, enabled flag, and available bytes.

Instructions

Get one storage definition (full config, secrets redacted) and its status/usage on each node. Pass node for that node's detailed status (active, enabled, available bytes).

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

Input Schema

NameRequiredDescriptionDefault
nodeNoAlso fetch detailed status on this node
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.6/5.0
Behavior3/5

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

Annotations already cover the safety profile: readOnly and closed-world. The description adds useful return-shape context (full config with secrets redacted, per-node usage fields active/enabled/available bytes). It doesn't explain error handling when the storage ID is unknown, and the odd idempotentHint=false is neither explained nor contradicted.

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, no filler, and the conditional node behaviour is front-loaded. Every phrase carries information an agent can act on.

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 two-parameter read tool with no output schema, the description covers the return contents, secrets redaction, and the node-vs-cluster distinction. Only edge cases (invalid storage ID, node unreachable) are left unstated.

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%, so the baseline is 3. The description does add a little meaning by saying the `node` parameter unlocks node-specific status fields, but this largely echoes the schema's own 'Also fetch detailed status on this node' text.

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 and resource: fetch one storage definition plus its status/usage per node. That separates it from list-style siblings such as proxmox_list_storage and proxmox_get_storage_stats, though the description itself doesn't name those alternatives (the schema does).

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?

The description says to pass `node` when node-level detail is wanted, which implies the default single-storage behaviour. It doesn't state when to prefer this over proxmox_get_storage_stats or proxmox_list_storage, so routing guidance is only implied.

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