Skip to main content
Glama

Get a node network interface

proxmox_get_node_network_interface
Read-only

Retrieve the stored configuration for a single Proxmox node network interface, including pending changes from /etc/network/interfaces.

Instructions

Get the configuration of one network interface on a node (as stored in /etc/network/interfaces, including pending changes).

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": {
      "iface": "<iface>"
    },
    "name": "proxmox_get_node_network_interface"
  }
}

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.
ifaceYesInterface name, e.g. vmbr0, bond0, eno1, vmbr0.20

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 cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds real context beyond them: the data source is /etc/network/interfaces and the result may include not-yet-applied pending changes, which matters for interpretation. It stops short of describing auth needs, the return shape, or how pending changes are distinguished.

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?

A single tight sentence with the resource and the scope up front and the file-source caveat parenthetically attached. Nothing is wasted and nothing essential is buried.

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 three-parameter read-only lookup with full schema coverage and no output schema, the description supplies what is needed: what is read, where it comes from, and that pending changes may be present. Only a hint about the raw flag's effect on output would make it fully self-sufficient.

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 100%, so all three parameters (node, iface, raw) are documented in the schema with examples and defaults. The description adds no further parameter meaning, such as what the raw flag changes about the response, so the baseline 3 applies.

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 states a specific verb and resource ('Get the configuration of one network interface on a node') and the singular 'one interface' implicitly separates it from the list-style sibling proxmox_list_node_network. It does not explicitly name an alternative, so differentiation is inferred rather than stated.

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 only implied: an agent can infer this is the per-interface lookup versus a listing call, but there is no explicit 'use this when X, use Y for all interfaces' routing. No prerequisites or exclusions are given.

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