Skip to main content
Glama

Get storage usage history

proxmox_get_storage_stats
Read-only

Summarize a storage's usage over time from RRD data, including current, min, max, and growth with sample points, to support capacity planning.

Instructions

Summarize a storage's usage over time from its RRD data (current, min, max, growth over the period) with a few sample points. Useful for capacity planning.

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

Input Schema

NameRequiredDescriptionDefault
cfNoConsolidation function (default AVERAGE)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
samplesNoNumber of evenly spaced sample points to include (default 12)
storageYesStorage ID, e.g. "local" or "local-lvm" (see proxmox_list_storage)
timeframeNoPeriod (default day)

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 declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real value by naming the RRD data source and the shape of what comes back, but it omits behavior an agent needs — what happens when no RRD data exists for the timeframe, how granularity/resolution limits sampling, and any cost of large timeframes.

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, zero padding, with the data source and returned measures front-loaded before the use case. Nothing could be removed without losing information.

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, the description usefully compensates by enumerating the returned summary fields and sample points. It is close to complete for a read-only stats tool, with the only gap being empty/missing-RRD-data behavior.

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 100%, including enum values for cf and timeframe and the defaults for samples and node, so the schema carries the parameter burden. The description only loosely gestures at 'a few sample points' and 'over the period' without adding format or resolution semantics 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?

The description gives a specific verb and resource ('Summarize a storage's usage over time from its RRD data') and enumerates the returned measures (current, min, max, growth), which separates it from the point-in-time sibling proxmox_get_storage. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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?

'Useful for capacity planning' implies a context but gives no explicit when-to-use vs when-not guidance and names no alternative tool for one-off current-usage lookups. The agent must infer that proxmox_get_storage covers snapshots while this covers history.

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