Skip to main content
Glama

List node network interfaces

proxmox_list_node_network
Read-only

List a Proxmox node's network interfaces—physical NICs, bridges, bonds, VLANs and OVS objects—with addresses, gateways, ports and comments, and flag inactive interfaces that may have pending changes.

Instructions

List a node's network configuration: physical NICs, Linux bridges, bonds, VLANs and OVS objects with addresses, gateways, ports and comments. Interfaces that are configured but not active are flagged; that usually means pending (unapplied) changes from proxmox_save_node_network_interface, or a down link. Apply with proxmox_apply_node_network or discard with proxmox_revert_node_network.

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

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the full unprocessed objects from the API (larger)
nodeNoNode name. Defaults to PROXMOX_DEFAULT_NODE, or the only node on a single-node install. See proxmox_list_nodes.
typeNoOnly this interface type (any_bridge = Linux and OVS bridges)
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

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 safety is covered; the description adds genuinely new context by explaining what an inactive-interface flag means and routing the agent to apply/revert tools. It does not mention pagination or result size behavior (relevant given the 'raw' parameter returns larger objects), which keeps it below 5.

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?

Content is front-loaded: the capability sentence comes first, then the inactive-interface interpretation, then remediation options. Three sentences with no filler, though the final sentence packs three tool names that add length without much new information beyond the apply/revert pair.

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 return-value burden and does so reasonably by listing the object families and attributes returned. All five parameters are optional and mostly covered by the schema; the description's gap is that it never explains the raw-format option, which matters for an agent handling large node configs.

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 80%, so the baseline is 3, but the description's enumeration of interface types (physical, bridges, bonds, VLANs, OVS) reinforces the 'type' enum semantics and the mention of addresses/gateways/ports/comments signals what each returned object carries. It still provides no meaning for 'raw', 'search', or 'fields' beyond what the schema already states.

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 opens with a specific verb and resource ('List a node's network configuration') and enumerates exactly what is covered: physical NICs, Linux bridges, bonds, VLANs, OVS objects, plus addresses, gateways, ports and comments. It does not, however, distinguish itself from the obvious sibling proxmox_get_node_network_interface (single-interface read), so an agent must infer the list-vs-get split.

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 gives clear situational context — interfaces configured but not active indicate pending unapplied changes — and names the follow-up actions (proxmox_apply_node_network, proxmox_revert_node_network) plus the tool that creates the pending state (proxmox_save_node_network_interface). What's missing is explicit guidance on when to reach for this versus proxmox_get_node_network_interface or the guest-interface siblings.

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