Skip to main content
Glama

pve_firewall_alias_delete

Delete a Proxmox firewall alias with a dry-run plan to preview before execution. Requires no active rule references; use creation tool to revert if needed.

Instructions

MUTATION: delete a firewall alias. Dry-run by default — the PLAN shows the current alias. PVE refuses while any rule still references the alias. No UNDO: re-create it with pve_firewall_alias_create to revert. Synchronous — confirm=True returns {"status": "ok", "result": None}; no task UPID to poll.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoGuest kind for scope='guest': 'qemu' or 'lxc'.
nameYesName of the alias to delete.
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).
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?

With no annotations, the description fully covers behavioral traits: it's a mutation, dry-run by default, synchronous with no task UPID, and the error condition when alias is referenced. This is comprehensive.

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 'MUTATION:' to immediately convey the action type. 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?

Given the tool's 8 parameters and mutation nature, the description covers key aspects: default behavior (dry-run), constraints (referenced alias), recovery (re-create), and response format. It is complete for an agent to use correctly.

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 by explaining the confirm parameter (dry-run vs execution) and the digest parameter (not surfaced in PLAN). It does not detail all parameters but provides critical context beyond the 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 is a mutation to 'delete a firewall alias' and distinguishes itself from related tools like pve_firewall_alias_create by explicitly mentioning re-creation for undo. The scope is well-defined with the dry-run default.

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?

It explicitly states that PVE refuses deletion if any rule references the alias, guiding users to remove references first. It also explains the dry-run behavior and how to revert via pve_firewall_alias_create, providing clear usage context.

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