Skip to main content
Glama

pve_sdn_fabric_node_delete

Remove a node from an SDN fabric. Use confirm=true to stage the removal and apply later; false returns a dry-run plan.

Instructions

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

Referential-integrity refusal is asserted BY ANALOGY only — Smoke-confirm. confirm=True stages the removal and returns {status, result}; no config UNDO — re-create the node to revert. RISK_MEDIUM (staging a removal an apply would enact).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
node_idYesExisting fabric node id to remove.
fabric_idYesExisting SDN fabric id.
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?

Given no annotations, the description well discloses mutation behavior, dry-run semantics, no digest/lock_token, referential-integrity by analogy, and risk level. Missing permission/rate limit details but covers key traits.

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

Conciseness3/5

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

The description is concise but includes unclear phrases like 'PENDING' and 'by ANALOGY — Smoke-confirm' that may confuse agents. Structure is adequate but not front-loaded with key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values are handled. However, the description lacks clarity on prerequisites (e.g., node must exist) and the 'PENDING' status. Provides risk and undo limitations but incomplete for a mutation tool.

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 detailed parameter descriptions. The tool description adds minimal extra meaning beyond the schema, only restating confirm behavior already in 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 'MUTATION: remove a node from an SDN fabric' and explicitly notes the upstream bug ('Add a node') to confirm deletion intent. This distinguishes it from sibling tools like pve_sdn_fabric_node_create.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Provides context on the confirm parameter (dry-run vs execute) and mentions no undo. However, it lacks direct comparisons to alternatives like pve_sdn_fabric_node_update or explicit when-not-to-use guidance.

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