Skip to main content
Glama

pve_network_iface_update

Modify an existing network interface's configuration (e.g., address, netmask) on a Proxmox node. Review the plan with dry-run, then confirm to stage the update.

Instructions

MUTATION: update an existing network interface config (staged — not live until pve_network_apply).

options carries fields to update (address, netmask, bridge_ports, …); the interface's type is preserved automatically and cannot be changed here — recreate via pve_network_iface_create for a type change. Dry-run by default (returns a PLAN); confirm=True stages the update and returns {status, result} — result is often None. RISK_MEDIUM (staged change, reversible before apply).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoNode the interface lives on; defaults to the configured node.
ifaceYesExisting interface name to update, e.g. vmbr1 or eth0.100.
confirmNoFalse (default) returns a dry-run PLAN only; True stages the update (still not live until pve_network_apply).
optionsNoFields to update: address, netmask, bridge_ports, etc.
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?

No annotations provided, but description fully covers behavioral aspects: it's a staged mutation, dry-run without confirmation, confirm stages, return format, and risk level. Type preservation is noted. No contradictions.

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 concise sentences plus a note. Front-loaded with 'MUTATION' and 'staged'. Every sentence adds value; 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?

Given the output schema exists (not shown), the description is self-contained: it explains staging, dry-run, confirm, type preservation, and risk. An agent can use this tool correctly without external context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage, but description adds crucial context: 'options' carries fields like address/netmask, and type is preserved automatically. It clarifies the confirm parameter's effect and the meaning of the result (often None).

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 it updates an existing network interface config and is staged until apply. It distinguishes from create (type change) and apply, making the purpose unambiguous.

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 explains when to use (existing interface update) and when not (type change requires recreate). Mentions dry-run by default and confirm behavior. Could explicitly name siblings like pve_network_iface_create, but the type change hint serves as a good guideline.

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