Skip to main content
Glama

pve_firewall_alias_update

Update a Proxmox firewall alias with a dry-run preview showing current values and changes. Changing the CIDR automatically updates all referencing firewall rules.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidrNo
kindNo
nameYes
nodeNo
vmidNo
scopeNocluster
digestNo
renameNo
commentNo
confirmNo
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?

No annotations provided, but description discloses dry-run behavior, mutation nature, and the side effect of altering referencing rules. Lacks information on error handling or permissions.

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?

Description is three sentences, no filler, front-loaded with key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 parameters and high complexity, description lacks parameter explanations and details about return values or error handling. Output schema exists but is not leveraged.

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 9%. Description does not explain any of the 11 parameters, leaving the agent to guess their meaning and usage.

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: update a firewall alias', providing a specific verb and resource. It distinguishes from sibling tools like create and 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?

Description mentions dry-run default and plan output, and warns about the side effect of changing CIDR. However, it does not explicitly compare with create or delete.

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