Skip to main content
Glama

Get container performance history

proxmox_get_container_stats
Read-only

Summarize an LXC container's RRD performance history with average, maximum, and latest CPU, memory, swap, disk, network, and I/O rates for a chosen timeframe; optionally return raw data points.

Instructions

Summarize an LXC container's performance history from RRD data: average, maximum and latest CPU %, memory, swap, disk usage, network and disk I/O rates over the chosen timeframe. Set points=true to also get the individual data points.

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": {
      "vmid": "<vmid>"
    },
    "name": "proxmox_get_container_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
cfNoRRD consolidation function (default AVERAGE)
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100
pointsNoAlso return the data points (compacted)
timeframeNoTime window (default hour)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4/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 value by naming the data source (RRD) and the shape of the result (average/max/latest summaries) and by flagging the points=true payload expansion. What it omits is that RRD retention bounds the usable timeframe values, which is the main behavioral gotcha for this tool.

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, front-loaded with the resource and the returned metrics, followed immediately by the one non-obvious option. No filler or restated name/title padding.

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 correctly compensates by enumerating what the response contains (summary aggregates of CPU, memory, swap, disk, network and I/O). It is nearly complete for a read-only stats tool; only the RRD retention caveat and the relative cost of points=true are 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 100%, so every parameter including cf, node, timeframe and points is already documented in the schema. The description only restates the timeframe and points semantics ('individual data points'), adding little beyond what the enum and descriptions supply. Baseline 3 applies when the schema carries the load.

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?

States a specific verb ('Summarize') and resource ('an LXC container's performance history from RRD data'), then enumerates exactly what is returned: average, maximum and latest CPU %, memory, swap, disk, network and disk I/O. The container scope plus metric list clearly separates it from proxmox_get_vm_stats and proxmox_get_node_stats without needing to name them.

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?

Usage is only implied: 'performance history ... over the chosen timeframe' tells an agent this is the historical-stats tool, and 'Set points=true to also get the individual data points' gives one concrete calling hint. There is no explicit statement of when to prefer this over sibling stats tools, nor any exclusion (e.g., live/current values vs RRD 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