Skip to main content
Glama

pve_sdn_fabric_create

Create a new SDN fabric as a staged mutation, pending until applied. Dry-run returns a plan; confirm executes the creation.

Instructions

MUTATION: create an SDN fabric (PENDING — inert until pve_sdn_apply).

To update an existing fabric use pve_sdn_fabric_update; to remove one use pve_sdn_fabric_delete. Dry-run by default (returns a PLAN); confirm=True creates the pending fabric, 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).
fabricYesNew SDN fabric id to create (2-8 chars, alnum + hyphen).
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
optionsNoProtocol-conditional fields (area, csnp_interval, hello_interval, ip_prefix, ip6_prefix, persistent_keepalive, redistribute, route_filter); PVE validates per protocol server-side. redistribute is schema-required for every protocol but only meaningful for ospf/bgp — omitting it for openfabric/wireguard is UNTESTED, Smoke-confirm.
protocolYesFabric routing protocol: openfabric, ospf, wireguard, or bgp.
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?

Despite no annotations, the description comprehensively discloses key behaviors: the mutation is PENDING and inert until pve_sdn_apply, dry-run by default returns a PLAN, confirm=True creates the pending fabric with status/result, and risk is LOW with no live network effect.

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 three concise sentences, each adding distinct value: first sentence states purpose and staging, second gives alternatives, third explains dry-run/confirm and risk. 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?

The description covers the essential workflow (pending, apply), risk, and parameter behavior. It lacks explanation of prerequisites or what happens after apply, but given the complexity and existence of pve_sdn_apply, it is mostly complete.

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?

With 100% schema coverage, the baseline is 3. The description adds value by explaining the confirm parameter's effect (dry-run vs execution) and the staging workflow, though it does not elaborate on other parameters 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 tool creates an SDN fabric, with the specific verb 'create' and resource 'SDN fabric'. It distinguishes from siblings by explicitly mentioning update (pve_sdn_fabric_update) and delete (pve_sdn_fabric_delete) tools.

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?

The description provides explicit guidance: use this tool to create a new fabric, use update for modifications, use delete for removal. It also explains when to use confirm=True (to execute) vs default dry-run behavior.

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