Skip to main content
Glama

pve_sdn_fabric_update

Update an existing SDN fabric. Dry-run returns a plan; confirm execution to stage changes for later application.

Instructions

MUTATION: update an SDN fabric (PENDING). To create a new fabric use pve_sdn_fabric_create; to remove one use pve_sdn_fabric_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 (e.g. ip_prefix/ip6_prefix/hello_interval/csnp_interval/route_filter for openfabric; area/redistribute/route_filter for ospf; ip_prefix/ip6_prefix/redistribute/route_filter/route_map_in/route_map_out for bgp; persistent_keepalive for wireguard).
digestNoExpected config digest for optimistic-concurrency checking.
fabricYesExisting SDN fabric id to update.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
optionsNoProtocol-conditional fields to set (area, csnp_interval, hello_interval, ip_prefix, ip6_prefix, persistent_keepalive, redistribute, route_filter).
protocolYesFabric routing protocol — REQUIRED on update too (the schema requires restating it; unlike controller/dns/ipam, where type is immutable and absent from PUT). Whether passing a DIFFERENT protocol than the fabric's current one re-types it or is rejected is undocumented — forwarded verbatim.
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
Behavior4/5

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

Discloses mutation type, dry-run mode, low risk, and staging. With no annotations, this is good coverage. Does not detail side effects of incorrect usage or auth needs, but the staging mechanism is well explained.

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?

Very concise: three sentences, front-loaded with 'MUTATION' and sibling references. No wasted words.

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?

Covers mutation, dry-run, staging, and sibling tools. With 8 parameters and output schema present, description is adequate for agent decision-making. Could add example of protocol change consequence, but schema fills most gaps.

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% with parameter descriptions. Description adds value by explaining dry-run vs confirm and risk level, but does not significantly enhance individual parameter meaning beyond schema. Baseline 3 is appropriate.

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 an SDN fabric' and distinguishes from create and delete siblings. The verb 'update' and resource 'SDN fabric' are specific, and the mention of create/delete tools provides differentiation.

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?

Explains dry-run default and confirm=True behavior, and that changes are staged until pve_sdn_apply. Mentions alternatives for creation/deletion. Could explicitly state 'use this to modify an existing fabric', but context is sufficient.

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