Skip to main content
Glama

pve_firewall_ipset_entry_add

Add an IP or CIDR network entry to a Proximo firewall IP set. Dry-run shows planned changes; use confirm=True to execute.

Instructions

MUTATION: add an IP/Network entry to an IP set. Dry-run by default — the PLAN shows the entry and warns it changes every referencing rule's match set. nomatch=True = exclusion. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

No UNDO: revert by removing the entry with pve_firewall_ipset_entry_remove.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidrYesIP address or CIDR network to add as a member entry.
kindNoGuest kind for scope='guest': 'qemu' or 'lxc'.
nameYesName of the IP set to add the entry to.
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
commentNoFree-text comment stored with the entry.
confirmNoSet True to execute the mutation; False (default) only returns a dry-run PLAN.
nomatchNoIf True, this entry is an exclusion (negative match) rather than an inclusion.
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 provided, the description fully compensates by disclosing that it is a mutation, dry-run by default, synchronous, has no task to poll, and that nomatch=True means exclusion. It also explains the impact on referencing rules and the no-undo nature.

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 extremely concise with three sentences, each serving a purpose: stating the mutation and dry-run default, explaining nomatch, and covering synchronous behavior and lack of undo. It is well front-loaded.

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 (10 parameters, 2 required, output schema present), the description provides sufficient detail for an agent to select and invoke it correctly. It covers the core behavior, safety (dry-run), execution, and remediation.

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 beyond the schema by explaining the overall dry-run/confirm workflow and the synchronous return format, which aids in understanding the parameter semantics and output.

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 adds an IP/Network entry to an IP set, with a specific verb and resource. It distinguishes from the sibling removal tool by mentioning 'No UNDO' and referencing pve_firewall_ipset_entry_remove as the revert operation.

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 the dry-run default behavior and how to execute with confirm=True. It also provides an alternative action (removing the entry) but does not explicitly state when not to use this tool or compare to other ipset-related siblings like pve_firewall_ipset_create.

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