Skip to main content
Glama

pve_sdn_subnet_delete

Delete an SDN subnet from a vnet, with dry-run plan by default. Specify vnet and subnet CIDR to stage removal.

Instructions

MUTATION: delete an SDN subnet (PENDING). subnet is the id from pve_sdn_subnet_list.

To create a subnet instead use pve_sdn_subnet_create. Dry-run by default (returns a PLAN); confirm=True stages the removal and returns {status, result}; no config UNDO — re-create the subnet to revert. RISK_MEDIUM (staging a removal an apply would enact).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
vnetYesSDN vnet name the subnet belongs to.
subnetYesSubnet id (CIDR) from pve_sdn_subnet_list 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?

Discloses mutation, pending status, dry-run behavior, confirm flag, no undo, and risk medium. Without annotations, the description fully informs about side effects.

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?

Description is front-loaded with purpose, each sentence adds necessary context, no redundant information. Very concise.

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?

Covers purpose, usage, parameters, behavior, risk, and irreversibility. With output schema present, description is complete for agent decision-making.

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% so baseline is 3. Description adds value by explaining 'subnet' as id from list and 'confirm' behavior. Slight improvement over 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 it is a mutation to delete an SDN subnet, and distinguishes from sibling tools like pve_sdn_subnet_create by mentioning alternatives.

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 when-to-use (delete), when-not-to-use (use create instead), dry-run default, confirm flag for execution, and notes irreversibility and risk level.

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