Skip to main content
Glama

pve_firewall_alias_update

Modify a Proxmox VE firewall alias by changing its CIDR, comment, or name. Dry-run previews changes; synchronous confirmation applies them.

Instructions

MUTATION: update a firewall alias. Dry-run by default — the PLAN shows the current alias and the fields being changed. Changing the CIDR silently alters every referencing rule's match set. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

Requires at least one of cidr/comment/rename. No UNDO — revert by setting it back to its prior value; to create a new alias instead use pve_firewall_alias_create.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidrNoNew IP address/CIDR the alias should resolve to; omit to leave unchanged.
kindNoGuest kind for scope='guest': 'qemu' or 'lxc'.
nameYesName of the existing alias to update.
nodeNoNode name, required for scope='guest'.
vmidNoGuest VMID/CTID, required for scope='guest'.
scopeNoFirewall scope: 'cluster' or 'guest' (no node-scope aliases in the PVE API).cluster
digestNoOptimistic-lock digest forwarded to PVE to abort if the alias changed; this tool's PLAN does not surface a digest to copy (only the rule tools do).
renameNoNew name to rename the alias to; omit to keep the current name.
commentNoNew free-text comment; omit to leave unchanged.
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?

Despite no annotations, the description discloses crucial behavioral traits: it is a mutation, dry-run by default, changing CIDR silently alters referencing rules, synchronous with no task UPID, and explains the return format. No contradictions.

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?

Six sentences, efficient and front-loaded with key information. Every sentence adds value with no unnecessary words. Clear structure.

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 (11 params, mutation with dry-run, side effects), the description covers all essential aspects: purpose, behavior, requirements, side effects, alternatives, and return value. Output schema exists, but description still explains the response format.

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 has 100% description coverage, so baseline is 3. The description adds extra context for key parameters (e.g., digest note about PLAN, scope explanation) and overall behavioral context, but not drastically beyond schema.

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 starts with 'MUTATION: update a firewall alias,' clearly stating the verb and resource. It distinguishes itself from sibling tools by mentioning that to create a new alias, use pve_firewall_alias_create instead.

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?

Explicitly describes the dry-run default, how to execute with confirm=True, requires at least one of cidr/comment/rename, and provides an alternative tool for creation. Also states there is no undo, guiding appropriate usage.

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