Skip to main content
Glama

pve_firewall_alias_create

Create a firewall alias (CIDR) that can be referenced by firewall rules. Use confirm=True to apply the change.

Instructions

MUTATION: create a firewall alias (named CIDR). Dry-run by default — the PLAN shows the name, CIDR, and scope. Re-call with confirm=True to execute. Passive until a rule references it. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

No UNDO: revert by deleting the alias with pve_firewall_alias_delete. To change an existing alias instead, use pve_firewall_alias_update.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cidrYesIP address or CIDR network the alias resolves to.
kindNoGuest kind for scope='guest': 'qemu' or 'lxc'.
nameYesName for the new alias, referenced by rules as this name.
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
commentNoFree-text comment stored with the alias.
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?

Discloses mutation, dry-run vs. execution, synchronous nature (no UPID), no undo (delete required), and passive until referenced by a rule. Return format for confirm=True is given.

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?

Concise two-paragraph structure with bullet points. Front-loaded 'MUTATION' label. Every sentence adds essential information without redundancy.

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?

Covers workflow (dry-run, confirm), safety (no undo), and sibling relationships. Output schema exists, so return format isn't needed. Enough for correct invocation.

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 covers all parameters (100% coverage). Description adds value by summarizing that the PLAN shows name, CIDR, and scope, and notes the confirm boolean. This provides context 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 clearly states it creates a firewall alias (named CIDR). It distinguishes from siblings by explicitly naming pve_firewall_alias_update for changes and pve_firewall_alias_delete for deletion.

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?

Describes dry-run default with PLAN output, re-call with confirm=True to execute. Provides guidance on when not to use (no UNDO, use delete) and alternative for changes (update).

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