Skip to main content
Glama

Get capacity and overcommit report

proxmox_get_capacity_report
Read-only

Compare guest vCPU, memory, and disk allocations against physical capacity per node and cluster to detect overcommitment; ratios cover running and all guests. Read-only.

Instructions

Compare what guests are allocated with the physical capacity, per node and for the cluster: vCPUs against the node's CPU threads, configured guest memory against the node's RAM, and (unless storage=false) the provisioned size of VM and container disks on each storage against its size, which shows thin-provisioning overcommit. Each figure is given for running guests and for all guests (as if every guest were started); templates are left out. A ratio above 1 means overcommitted. Read-only. The storage part lists the disk volumes on each storage, so it takes longer on big clusters.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoOnly this node (and its storage)
storageNoInclude storage allocation (default true)

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 the 'Read-only' sentence is largely redundant. The description still earns credit for behavior beyond the annotations: templates are excluded from the figures, each metric is reported both for running guests and for all guests, and the storage section has a material performance cost on large clusters.

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?

The core comparison is front-loaded in the first sentence and every later sentence adds a distinct fact (guest cohorts, template exclusion, ratio interpretation, storage tradeoff). It is a single dense paragraph with long clauses, but there is no filler.

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 carries the burden of explaining the result, and it does: it defines both guest cohorts, the meaning of the ratio, and what is excluded. Only the concrete shape of the returned figures is left unspecified, which is acceptable for a read-only report.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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, but the description genuinely adds meaning: it clarifies that 'node' also narrows the storage scope, and that storage=false removes the provisioned-vs-actual disk comparison rather than just hiding a field. It also states the default (true) and the cost of leaving it on.

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 uses a precise verb (compare) with clearly enumerated resources: vCPUs vs CPU threads, guest memory vs node RAM, provisioned disk size vs storage size. It is far more specific than the title, but it never names or rules out the obvious overlapping sibling (proxmox_get_node_report), so an agent must still infer the boundary.

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 implied rather than stated: the 'ratio above 1 means overcommitted' framing signals capacity-planning use, and the note that the storage portion 'takes longer on big clusters' implies when to pass storage=false. There is no explicit when-to-use, when-not-to-use, or named alternative.

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