Skip to main content
Glama

pve_firewall_security_group_delete

Delete a cluster security group in Proxmox VE. Dry-run by default shows a plan; set confirm=True to execute. Group must be empty and unused to proceed.

Instructions

MUTATION: delete a cluster security group. Dry-run by default — the PLAN shows how many rules the group holds. PVE refuses while the group is non-empty or still referenced by a rule. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

No UNDO: re-create it with pve_firewall_security_group_create and re-add its rules to revert.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupYesName of the cluster security group to delete.
confirmNoSet True to execute the mutation; False (default) only returns a dry-run PLAN.
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 are provided, so the description carries full burden. It discloses mutation, dry-run behavior, synchronous nature, return format, and refusal conditions. However, it does not cover idempotency or authorization requirements, leaving minor gaps. Still highly transparent.

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?

The description is three concise sentences that front-load the mutation nature and key dry-run behavior. Every sentence adds essential information without redundancy, making it highly efficient.

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's complexity (delete with dry-run, conditions, synchronous), the description covers most critical aspects: return values for confirm=True, refusal conditions, and undo method. The output schema likely fills remaining details. Slight omission of PLAN format details but acceptable.

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 description coverage is 100%, so baseline is 3. The description adds value beyond schema by explaining the PLAN output, synchrony, and the effect of confirm=True. This enhances understanding of parameter behavior.

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 cluster security group, using the specific verb 'delete' and resource 'cluster security group'. It distinguishes from the sibling tool pve_firewall_security_group_create by mentioning re-creation as the undo method.

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?

The description explicitly explains usage: dry-run by default, conditions under which PVE refuses (non-empty or referenced), synchronous execution with confirm=True, and provides a clear alternative for undoing via pve_firewall_security_group_create. This gives excellent guidance on when and how to use the tool.

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