Skip to main content
Glama

Get container configuration

proxmox_get_container_config
Read-only

Retrieve an LXC container's stored Proxmox configuration, including current, pending, or snapshot values, and return a digest for optimistic-locking updates.

Instructions

Get an LXC container's full configuration as stored by Proxmox (secrets redacted). Options: current=true for the running values instead of pending ones, snapshot to read the config as saved in a snapshot, or pending=true to list each key with its current and pending value. The returned digest can be passed to proxmox_update_container_config for optimistic locking.

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

Input Schema

NameRequiredDescriptionDefault
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100
currentNoReturn current values instead of values including pending changes
pendingNoReturn the key/current/pending listing from the pending endpoint instead
snapshotNoRead the config saved in this snapshot

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/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, and the description adds genuinely useful context: secrets are redacted and the returned digest supports optimistic locking via proxmox_update_container_config. However it does not describe the shape of the returned config or how snapshot/pending combinations behave, so it remains additive but partial. Note the idempotentHint=false is unusual for a read tool, though the description does not contradict it.

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?

Three sentences, front-loaded with the core action before the option enumeration; every clause carries information. Slightly dense phrasing ('Options: current=true ... or pending=true ...') but no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, no-output-schema tool with all five parameters documented, the description covers the essential gaps: redaction of secrets, the three mode behaviors, and the usable digest for follow-up writes. Nothing an agent needs in order to call it correctly is missing.

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; the description earns more by clarifying the current-vs-pending relationship and by framing snapshot as 'read the config as saved in a snapshot', which is more informative than the schema's terse 'Read the config saved in this snapshot'. The digest/locking note further ties a return value to a downstream parameter.

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 and resource ('Get an LXC container's full configuration as stored by Proxmox') and scopes it to stored config, which implicitly distinguishes it from runtime siblings like proxmox_get_container or proxmox_get_container_stats and from proxmox_get_vm_config. An agent knows exactly what it retrieves.

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?

Explains the three read modes (current, snapshot, pending) with their conditions, which is real when-to-use guidance for parameter selection. It stops short of naming an alternative tool or stating when not to use this one, so a 4 rather than a 5.

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