Skip to main content
Glama

pve_firewall_ipset_entry_remove

Remove an IP or CIDR entry from a Proxmox IP set. Dry-run shows the plan; confirm to execute.

Instructions

MUTATION: remove an IP/Network entry from an IP set. Dry-run by default — the PLAN shows the entry and warns it changes every referencing rule's match set (may open or close access). Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

No UNDO: revert by re-adding the entry with pve_firewall_ipset_entry_add.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidrYesIP address or CIDR network of the member entry to remove.
kindNoGuest kind for scope='guest': 'qemu' or 'lxc'.
nameYesName of the IP set to remove the entry from.
nodeNoNode name, required for scope='guest'.
vmidNoGuest VMID/CTID, required for scope='guest'.
scopeNoFirewall scope: 'cluster' or 'guest' (no node-scope ipsets in the PVE API).cluster
digestNoOptimistic-lock digest forwarded to PVE to abort if the set changed; this tool's PLAN does not surface a digest to copy (only the rule tools do).
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?

Without annotations, the description covers key behavioral traits: mutation, dry-run default, synchronous execution, no undo, and the effect on referencing rules. It also notes that confirm=True returns a specific result with no task UPID to poll.

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 sentences long, front-loads purpose and type, and efficiently covers behavior, result, and recovery. No redundant information.

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 tool's complexity (9 parameters, 2 required) and the presence of an output schema, the description provides sufficient context: purpose, behavior (dry-run, synchronous, no undo), result format, and reversion method. It also warns about the impact on referencing rules.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents each parameter. The description does not add new parameter-specific meaning beyond the schema, so a baseline score of 3 is appropriate.

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's purpose: 'remove an IP/Network entry from an IP set.' It uses a specific verb ('remove') and resource ('IP set entry'), distinguishing it from siblings like pve_firewall_ipset_entry_add and pve_firewall_ipset_delete.

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 explains that by default it's a dry-run (PLAN), and that to revert you use the add tool. However, it does not explicitly state when to use this over alternatives or provide when-not conditions.

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