Skip to main content
Glama

pve_firewall_rule_update

Update an existing firewall rule at a specific position. Dry-run first shows changes and optimistic-lock digest; confirm with digest to prevent concurrent updates.

Instructions

MUTATION: update an existing firewall rule at position pos. Dry-run by default — the PLAN shows the rule's current state, the fields being changed, AND the optimistic-lock digest. Pass the digest from the plan back as digest= on confirm so PVE rejects the update if the rule list moved since the preview (positions shift and the wrong rule can be updated otherwise). Synchronous.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
posYes
destNo
kindNo
nodeNo
vmidNo
dportNo
protoNo
scopeNocluster
sportNo
actionNo
digestNo
enableNo
sourceNo
commentNo
confirmNo
directionNo
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?

With no annotations, the description carries full burden. It discloses the tool is a mutation, dry-run by default, synchronous, and uses optimistic locking with digest. It also warns about position shifts. Missing details like authorization or side effects, but the core behavioral traits are well covered.

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 (three sentences) and front-loaded with the purpose. It adds critical workflow details without extraneous text. Every sentence earns its place.

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?

Despite many parameters, the description covers the essential update workflow (position, dry-run, confirm, digest). Optional parameters are intuitive from their names. The existence of an output schema reduces the need to explain return values. The description is sufficient for an agent to use the tool correctly in most cases.

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

Parameters2/5

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

Schema description coverage is only 6%, so the description must compensate. It explains `pos`, `digest`, and `confirm` but leaves many other parameters (e.g., `dest`, `kind`, `node`, `vmid`) unexplained. Agents must rely on parameter names alone, which is insufficient for correct invocation.

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?

Clearly states the tool's purpose: 'update an existing firewall rule at position `pos`.' The verb 'update' and resource 'firewall rule' are explicit, and the positional parameter distinguishes it from sibling tools like pve_firewall_rule_add or pve_firewall_rule_remove.

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?

Describes the dry-run-and-confirm workflow and warns about position shifts requiring a digest for optimistic locking. While it does not explicitly state when not to use this tool, the workflow guidance effectively tells the agent how to use it correctly.

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