Skip to main content
Glama

pve_sdn_zone_delete

Delete an SDN zone safely: review a dry-run plan first, then confirm to stage the removal. Re-create the zone to revert.

Instructions

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

To create a zone instead use pve_sdn_zone_create. PVE refuses if a vnet still references it. confirm=True stages the removal and returns {status, result}; no config UNDO — re-create the zone to revert. RISK_MEDIUM (staging a removal an apply would enact).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zoneYesExisting SDN zone id to delete.
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.
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?

With no annotations, the description fully discloses behavior: dry-run by default, confirm stages removal, no config UNDO, risk medium, and re-create to revert. Comprehensive transparency.

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?

Concise yet informative. Uses clear structure: mutation label, purpose, dry-run explanation, alternative tool, constraints, and risk. Every sentence adds value without redundancy.

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?

Given high schema coverage, presence of output schema, and tool simplicity, the description covers all essential aspects: operation, parameters, risk, and constraints. No gaps.

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%, baseline 3. The description adds value by explaining the confirm parameter's role (dry-run vs execute) and the overall workflow, though lock_token and proximo_target are not elaborated beyond 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 'delete an SDN zone' and specifies it's a mutation. It distinguishes from the sibling pve_sdn_zone_create, making the purpose unambiguous.

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: use pve_sdn_zone_create for creation, notes that PVE refuses if vnet references it, explains dry-run default and confirm flag, and warns of no undo. Full usage context.

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