Skip to main content
Glama

pbs_node_network_reload

Apply staged network configuration changes on a PBS node. Dry-run by default to preview changes; use confirm=true to execute, with connectivity-lockout risk.

Instructions

MUTATION (HIGH): apply staged network configuration changes on a PBS node — makes interfaces.new live. Dry-run by default. *** CONNECTIVITY-LOCKOUT RISK *** a misconfigured interface can drop SSH/API access; recovery requires console/physical access. confirm=True executes (PUT /nodes/{node}/network) and returns {"status": "ok", "result": None}. Review staged changes with pbs_node_network_list first; discard them instead with pbs_node_network_revert. Needs PROXIMO_PBS_* config.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nodeNoPBS node name (or 'localhost').localhost
confirmNoFalse (default) returns a dry-run PLAN only; True applies the staged changes.
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?

Labels itself 'MUTATION (HIGH)' and warns of connectivity-lockout risk. Describes behavior: confirm=False gives dry-run plan, confirm=True executes (PUT) and returns specific response. No annotations provided, so description fully covers behavioral traits.

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?

The description is concise (~5 sentences) and well-structured: mutation indication, purpose, dry-run note, risk warning, confirm behavior, sibling references, config requirement. No redundant information.

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 an output schema exists, the description still provides important context: HTTP method, return values for confirm=True, prerequisites (PROXIMO_PBS_* config), risk warning, and references to complementary tools. Sufficient for an agent to use the tool effectively.

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 covers 100% of parameters with descriptions. The description adds context: dry-run default for confirm, workflow references, and risk. While schema already explains each param, the description reinforces the confirm parameter's role and the overall effect.

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's purpose: 'apply staged network configuration changes on a PBS node — makes interfaces.new live.' It distinguishes from siblings like pbs_node_network_list (review) and pbs_node_network_revert (discard).

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?

Explicitly says 'Dry-run by default' and warns about connectivity-lockout risk. Provides alternatives: 'Review staged changes with pbs_node_network_list first; discard them instead with pbs_node_network_revert.' Mentions need for PROXIMO_PBS_* config.

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