Skip to main content
Glama

pve_sdn_prefix_list_entry_delete

Delete a prefix-list entry from an SDN prefix list. Use dry-run to preview the removal; confirm=True stages the deletion.

Instructions

MUTATION: delete a prefix-list entry (PENDING). Dry-run by default — the PLAN shows the current entry (may fail to read if entry_id is stale — disclosed, not hidden). confirm=True stages the removal and returns {status, result}; no config UNDO — re-create the entry to revert. RISK_MEDIUM.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoFalse (default) returns a dry-run PLAN only; True executes the staged mutation.
entry_idYesOPAQUE entry path token (the schema's {url_seq}) — capture from a prior list/get read.
lock_tokenNoSDN cluster lock token to use for this write, if one is held.
prefix_listYesExisting SDN prefix list 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
Behavior5/5

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

No annotations provided, so description fully handles transparency. It discloses mutation, dry-run default, confirm behavior, irreversibility (re-create to undo), stale entry failure, and risk level. No contradictions.

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 sentences, front-loaded with purpose and default behavior, then confirmation and risk. No wasted words, clear structure.

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

Completeness5/5

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

With output schema present, description covers all necessary aspects: operation, dry-run, confirmation, undo limitations, stale entry warning. Complete for an agent to invoke correctly.

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 has 100% coverage, so baseline is 3. The description adds value by clarifying entry_id as opaque and sourced from prior reads, and explaining the confirm parameter's role, going beyond schema descriptions.

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 deletes a prefix-list entry, with specific verb and resource. It distinguishes from sibling tools like create, get, and update by focusing on deletion with dry-run behavior.

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 implies usage for deleting entries but does not explicitly compare with alternatives or state when not to use. It provides context on dry-run and confirmation but lacks explicit guidance on tool selection.

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