Skip to main content
Glama

pbs_node_network_iface_create

Create a network interface configuration on a Proxmox PBS node. Dry-run checks for name collisions; set confirm=True to execute the plan.

Instructions

MUTATION (MEDIUM): create a network interface configuration on a PBS node (staged, written to interfaces.new — NOT live until pbs_node_network_reload). Dry-run by default (checks for a name collision). confirm=True executes (POST /nodes/{node}/network) and returns {"status": "submitted", "result": None}. Apply with pbs_node_network_reload (RISK_HIGH) or discard with pbs_node_network_revert. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPBS node name (or 'localhost').localhost
ifaceYesNew network interface name.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the creation.
optionsNoAdditional interface fields (cidr, gateway, bridge_ports, bond_mode, mtu, autostart, comments, ...) forwarded verbatim.
iface_typeNoInterface type: one of loopback, eth, bridge, bond, vlan, alias, unknown. PBS marks this OPTIONAL even on create.
proximo_targetNoWhich configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It discloses that the tool is a mutation, does not immediately apply changes (staged to interfaces.new), requires a reload to take effect, and performs a dry-run by default (checks for name collisions). The return value for confirm=True is also given. Behavioral traits are comprehensively covered.

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?

The description is well-structured and front-loaded with the mutation indication. Every sentence adds value, covering lifecycle, defaults, and related tools. It is concise yet comprehensive, though slightly dense.

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?

Given the complexity of the tool (staged mutation, dry-run, reload requirement), the description covers the essential workflow, output for execution, and config prerequisite. It lacks details on error handling or edge cases, but overall is sufficiently complete for an agent to use correctly.

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 coverage is 100%, so the description does not heavily supplement parameter meaning. The description reiterates the confirm parameter's role (dry-run vs execute) but does not add significant new information beyond the schema. The 'options' parameter is already well-described in the schema. Score reflects adequate but not enhanced clarity.

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 clearly states the tool creates a network interface configuration on a PBS node. It distinguishes from sibling tools by noting it is staged, requires reload, and mentions dry-run vs execute behavior. The verb 'create' and resource 'network interface configuration' are specific and unambiguous.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (to create a staged interface) and what to do afterward (apply with pbs_node_network_reload or discard with pbs_node_network_revert). It also mentions the dry-run default and that confirm=True executes the creation. Usage context and alternatives are clearly provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/john-broadway/proximo'

If you have feedback or need assistance with the MCP directory API, please join our Discord server