Skip to main content
Glama

pve_sdn_prefix_list_delete

Delete an SDN prefix list. Dry-run returns a plan of the current list; set confirm=true to stage removal, risking failure if other resources reference the list.

Instructions

MUTATION: delete an SDN prefix list (PENDING). Dry-run by default — the PLAN shows the current list.

Referential-integrity refusal (e.g. a fabric's route_filter still naming this list) 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 list 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.
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
prefix_listYesExisting SDN prefix list id to delete.
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?

No annotations provided, so the description carries the full burden. It discloses key behaviors: mutation, dry-run by default, confirm flag, no UNDO, RISK_MEDIUM, and referential integrity concern. This provides good transparency beyond the schema.

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 relatively concise but contains awkward phrasing like 'asserted BY ANALOGY... — Smoke-confirm.' While front-loaded with key info, some sentences could be tightened.

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 complexity (4 parameters, output schema exists), the description covers dry-run, confirm, no undo, risk, and referential integrity. It mentions return format on confirm and provides enough context for safe usage, though dry-run output details are not specified.

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%, so baseline is 3. The description adds minimal extra meaning for parameters beyond what the schema already provides (e.g., confirm behavior is restated). No added value for lock_token or proximo_target.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states 'delete an SDN prefix list' and mentions the dry-run behavior. The purpose is clear, though the qualifier '(PENDING)' is ambiguous. The name itself distinguishes from sibling prefix 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 Guidelines3/5

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

The description explains that dry-run is the default and confirm=True stages the removal, and warns about referential integrity. However, it does not explicitly state when to use this tool versus alternatives like pve_sdn_prefix_list_update or provide explicit when-not scenarios.

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