Skip to main content
Glama

pve_sdn_fabric_node_create

Add a node to an SDN fabric. Dry-run returns a plan; confirm executes the pending creation.

Instructions

MUTATION: add a node to an SDN fabric (PENDING — inert until pve_sdn_apply).

To update an existing node use pve_sdn_fabric_node_update; to remove one use pve_sdn_fabric_node_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending node, returning {status, result}. RISK_LOW (staging, no live network effect).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
digestNoExpected config digest for optimistic-concurrency checking — accepted on CREATE for this endpoint (one of three exceptions on this SDN plane to the 'digest never on create' convention).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
node_idYesFabric node id to create (a PVE cluster node hostname).
optionsNoProtocol-conditional fields (interfaces, ip, ip6, peers, allowed_ips, endpoint, public_key, role); PVE validates per protocol server-side.
protocolYesFabric routing protocol: openfabric, ospf, wireguard, or bgp — must match the fabric's own configured protocol.
fabric_idYesExisting SDN fabric id to add this node to.
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 key behavioral traits: the mutation is pending until pve_sdn_apply, the dry-run default, the effect of confirm=True, and the returned object structure. Also notes RISK_LOW for staging. Without annotations, this covers the most relevant behaviors, though minor details like lock token handling could be added.

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 extremely concise—3 sentences—with the most critical information (purpose, pending nature, sibling alternatives, dry-run vs confirm) front-loaded. Every sentence provides essential guidance without waste.

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 tool's complexity (8 params, 3 required, output schema present), the description covers the workflow, risk level, and sibling differentiation. It could elaborate on return value details, but the output schema exists to fill that gap. Overall, it's 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.

Parameters4/5

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

All 8 parameters are described in the schema (100% coverage). The description adds extra context for the 'options' parameter, listing protocol-conditional fields and noting server-side validation. It also mentions the digest exception. This adds meaningful value beyond the schema.

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 verb 'add' and the resource 'node to SDN fabric', and uses the prefix 'MUTATION' to signal it's a write operation. It also distinguishes from sibling tools for update and delete, 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 Guidelines5/5

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

Explicitly provides when to use this tool vs alternatives by naming pve_sdn_fabric_node_update and pve_sdn_fabric_node_delete. Also explains the default dry-run behavior and when to set confirm=True, providing clear context for invocation.

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