Skip to main content
Glama

pve_sdn_fabric_delete

Delete an SDN fabric from Proxmox. Use 'confirm' to execute the deletion or false for a dry-run plan.

Instructions

MUTATION: delete an SDN fabric (PENDING). Upstream's own description for this endpoint says "Add a fabric" — a confirmed copy-paste bug; this deletes. NO digest and NO lock_token parameter exists for this endpoint at all (schema-verified — unlike every other delete on this SDN plane).

Referential-integrity refusal (e.g. an EVPN zone's own 'fabric' field still naming this fabric) is asserted BY ANALOGY to the zone/vnet precedent, not independently confirmed against this endpoint's own schema — Smoke-confirm. confirm=True stages the removal and returns {status, result}; no config UNDO — re-create the fabric to revert. RISK_MEDIUM (staging a removal an apply would enact).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fabricYesExisting SDN fabric id to delete.
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
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 provided, so description fully discloses mutation nature, staging behavior, lack of undo, and risk. Also notes analogies and need for smoke-confirmation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is detailed but front-loaded with purpose. Some redundancy in explaining analogies, but overall well-structured and informative.

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 most contextual aspects: staging, risk, analogies, special parameters. Output schema exists, so return values not needed. Could mention when to use rollback, but adequate.

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%, description adds limited extra value beyond schema descriptions (e.g., return format for confirm). Baseline 3 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?

Description clearly states 'delete an SDN fabric' and highlights a copy-paste bug in upstream description, distinguishing it from sibling tools like pve_sdn_fabric_create.

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?

Provides explicit guidance on missing digest/lock_token (unlike other SDN deletes), referential-integrity behavior by analogy, confirm=True staging action, and risk level (MEDIUM).

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