Skip to main content
Glama

List SDN fabrics

proxmox_list_sdn_fabrics
Read-only

Lists Proxmox SDN fabrics and their nodes; optionally reads live routes, neighbors, and interfaces for a given node and fabric.

Instructions

List SDN fabrics (PVE 9 underlay networks: OpenFabric, OSPF, WireGuard, BGP) with their nodes. Give node and fabric to also read that node's live fabric routes, neighbors and interfaces. Read-only; fabrics are edited in the web UI or with proxmox_api_request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_sdn_fabrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoWith `fabric`: read this node's live routes/neighbors/interfaces for the fabric
fabricNoFabric ID for the live node status
pendingNoInclude uncommitted changes: each object shows `state` (new/changed/deleted) and the `pending` values not yet applied with proxmox_apply_sdn
runningNoShow the running (last applied) configuration instead of the edited one

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description's 'Read-only' largely restates that. It does add useful behavior beyond annotations: the two-mode operation (static fabric inventory vs. live node state) and the fact that fabrics cannot be modified here. It omits any statement about result volume, ordering, or why idempotentHint is false for a pure read.

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?

Three tight sentences with no filler: scope first, the parameter-driven mode second, the read-only/mutation boundary last. Every sentence carries distinct information.

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?

With no output schema, the description does the necessary work by naming the returned entities (fabrics with their nodes; routes, neighbors, interfaces in live mode). A little more on the base list's return shape (e.g., that pending/running select the config version) would close the remaining gap.

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%, so the baseline is 3, but the description adds the pairing rule that `node` alone is insufficient and must be combined with `fabric` to trigger the live-status branch. It also ties `pending` to proxmox_apply_sdn, giving the uncommitted-changes flag an operational meaning beyond the schema text.

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?

States a specific verb and resource ('List SDN fabrics') and immediately qualifies scope by enumerating the fabric types covered (OpenFabric, OSPF, WireGuard, BGP) and noting the PVE 9 underlay-network domain. It also carves out a distinct second mode (per-node live status) and points mutation work elsewhere, so an agent can separate it from generic SDN list tools.

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?

Explicitly says to supply both `node` and `fabric` when the live routes/neighbors/interfaces view is wanted, and explicitly redirects editing to the web UI or proxmox_api_request. The only gap is that it doesn't contrast itself with the closest siblings (sdn_objects, sdn_status) for the plain list case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools