Skip to main content
Glama

List containers

proxmox_list_containers
Read-only

Lists LXC containers across a Proxmox cluster with status, node, CPU, memory, disk, uptime, tags, and pool; filter by node, status, search, templates, or result limit.

Instructions

List LXC containers across the cluster with status, node, CPU, memory, disk, uptime, tags and pool. For VMs and containers together use proxmox_list_guests.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoOnly containers on this node
limitNoMaximum number of results (default 500)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields
statusNoOnly containers in this state
templatesNoHow to treat templates (default include)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/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 value beyond them by enumerating the fields returned (status, node, CPU, memory, disk, uptime, tags, pool), which matters since there is no output schema. It does not mention pagination or the effect of the 'raw' flag, which is a minor gap.

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 filler: the capability and return payload come first, followed immediately by the sibling routing note. Nothing is repeated from the title or schema.

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 read-only list tool with no output schema, the description adequately covers what is returned and when to prefer the alternative; annotations cover safety. The only omission is any hint about result volume or default limiting, which the schema handles for the limit parameter.

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 86%, so the schema already explains node, status, templates, search, limit and raw. The description adds no parameter-level meaning beyond that, leaving the baseline of 3.

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?

The description gives a specific verb and resource ('List LXC containers') plus scope ('across the cluster') and enumerates the returned attributes. It explicitly names the sibling proxmox_list_guests as the tool for the combined VM+container case, so an agent can distinguish them without opening either schema.

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

Usage Guidelines4/5

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

It states the routing condition for the main alternative: use proxmox_list_guests when VMs and containers are both wanted. That is clear context for the primary ambiguity, though it gives no guidance on the filtering options (node/status/templates/search) that would help choose arguments.

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