Skip to main content
Glama

pve_firewall_ipset_delete

Delete a firewall IP set in Proxmox VE. Dry-run shows plan; use force to wipe members before deletion. Confirm to execute; no undo available.

Instructions

MUTATION: delete an IP set. Dry-run by default — the PLAN shows member count and the force semantics. force=True WIPES all members; PVE refuses while a rule references the set. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

No UNDO: re-create it with pve_firewall_ipset_create and re-add members to revert.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoGuest kind for scope='guest': 'qemu' or 'lxc'.
nameYesName of the IP set to delete.
nodeNoNode name, required for scope='guest'.
vmidNoGuest VMID/CTID, required for scope='guest'.
forceNoIf True, wipe all member entries so the (now-empty) IP set can be deleted.
scopeNoFirewall scope: 'cluster' or 'guest' (no node-scope ipsets in the PVE API).cluster
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
Behavior5/5

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

With no annotations, the description fully discloses mutation, dry-run, synchronous operation, no undo, force wiping all members, and the constraint related to rule references. This gives the agent a complete behavioral picture.

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 concise with front-loaded purpose, uses dash-separated points for clarity, and every sentence contributes essential information 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 the 8 parameters, 100% schema coverage, and presence of output schema, the description covers all critical aspects: mutation type, dry-run, force, synchronous, revert strategy, and behavioral constraints. It is sufficient for correct tool invocation.

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. The description adds value by explaining 'force=True WIPES all members' and the dry-run/confirm mechanism, which go beyond the schema's short 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 'MUTATION: delete an IP set' which is a specific verb+resource. It distinguishes from sibling tools like pve_firewall_ipset_create for creation and pve_firewall_ipset_entry_add/remove for individual entries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides explicit guidance on dry-run default, force semantics, synchronous behavior, and revert procedure via pve_firewall_ipset_create. It does not explicitly exclude using for individual entry deletion, but that is implied by the tool name and siblings.

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