Skip to main content
Glama

pve_sdn_fabric_node_update

Updates an existing SDN fabric node's settings. Dry-run returns a plan; use confirm=true to stage the change for later apply.

Instructions

MUTATION: update a fabric node (PENDING). To create a new node use pve_sdn_fabric_node_create; to remove one use pve_sdn_fabric_node_delete. Dry-run by default (returns a PLAN); confirm=True stages the edit and returns {status, result}. RISK_LOW (staging; inert until pve_sdn_apply).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deleteNoField name(s) to unset — the valid enum is protocol-conditional (interfaces/ip/ip6 for bgp/openfabric/ospf; allowed_ips/endpoint/interfaces/ip/ip6/peers for wireguard).
digestNoExpected config digest for optimistic-concurrency checking.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
node_idYesExisting fabric node id to update.
optionsNoProtocol-conditional fields to set (interfaces, ip, ip6, peers, allowed_ips, endpoint, public_key, role).
protocolYesFabric routing protocol — REQUIRED on update too (the schema requires restating it). Whether passing a DIFFERENT protocol re-types the node or is rejected is undocumented — forwarded verbatim.
fabric_idYesExisting SDN fabric id.
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
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 exist, so description carries full burden. It discloses mutation nature, dry-run vs. staging, risk level, and even caveats about the protocol field being required and undocumented behavior on change.

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?

Extremely concise with front-loaded key info (MUTATION, purpose, siblings, behavior). Every sentence provides necessary guidance with no fluff.

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?

With output schema present, description doesn't need to detail return values, but it does explain dry-run PLAN and confirm result. Also covers risk, sibling tools, and protocol caveat. Fully complete for a mutation tool.

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 100%, but description adds useful context beyond schema: explains delete for unsetting fields with protocol-conditional enums, options as protocol-conditional, and protocol being required on update. Adds significant value.

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?

Clearly states 'update a fabric node' and distinguishes from sibling create/delete tools. Verb+resource is 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?

Explicitly describes when to use (update) and when not (use create/delete siblings). Also explains dry-run default and confirm=True behavior, plus risk level and dependency on pve_sdn_apply.

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