Skip to main content
Glama

Get container IP addresses

proxmox_get_container_interfaces
Read-only

Retrieve live network interfaces and IPv4/IPv6 addresses inside a running LXC container, including DHCP/SLAAC addresses omitted from its configuration.

Instructions

Get the live network interfaces and IP addresses (IPv4 and IPv6) inside a running LXC container, including addresses obtained via DHCP/SLAAC that the config doesn't show. The container must be running.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100

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 this a read-only, closed-world operation; the description adds genuinely useful behavioral context beyond them — that results reflect live runtime state (including DHCP/SLAAC leases) and that the container must be running. It does not address what happens when the container is stopped or how results look if no addresses are assigned, so it is good rather than complete.

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 short sentences: the capability and scope first, the precondition second. No filler, no repetition of the title or annotations.

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 simple read tool with full schema coverage and no output schema, the description covers what is returned (interfaces and IPv4/IPv6 addresses) and the operational precondition. Only the behavior on a stopped container or an address-less container is left unstated.

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?

All three parameters are fully documented in the schema (100% coverage), including the node auto-lookup and raw flag, so the baseline is 3. The description adds no parameter-level meaning of its own, which is acceptable when the schema does the work.

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 pairs a specific verb and resource ('Get the live network interfaces and IP addresses ... inside a running LXC container') and explicitly scopes it beyond config data by including DHCP/SLAAC addresses 'that the config doesn't show'. That contrast lets an agent distinguish it from proxmox_get_container_config 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 a clear precondition ('The container must be running') and implicitly routes the agent here when live rather than configured addressing is needed. It stops short of naming an explicit alternative for stopped containers or for static-config lookups, so guidance is clear but not fully exhaustive.

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