Skip to main content
Glama

List firewall macros

proxmox_list_firewall_macros
Read-only

Lists predefined Proxmox VE firewall macros such as SSH, HTTP, and DNS so you can use a macro in a rule instead of specifying protocol and port.

Instructions

List the predefined firewall macros (SSH, HTTP, DNS, Ceph, ...) usable as a rule's macro instead of proto/port.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proxmox_list_firewall_macros"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
searchNoCase-insensitive substring filter on names, IDs, tags and similar fields

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the set is predefined/built-in, which hints at a small static result set, but says nothing about return shape, whether filtering happens server-side, or result size.

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?

A single sentence with no filler, front-loading the action and resource and using the trailing clause for essential context. Nothing could be removed without losing information.

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?

For a simple, safe, read-only enumeration tool with no output schema and annotations covering safety, the description is nearly sufficient. The remaining gap is the undocumented 'fields' parameter, which the description does nothing to compensate for.

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?

At 50% schema coverage, only the 'search' parameter is documented (in the schema itself), while 'fields' has no description anywhere. The description mentions neither parameter, so it adds zero meaning beyond the schema and leaves the projection parameter fully unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List the predefined firewall macros') and grounds it with concrete examples (SSH, HTTP, DNS, Ceph) plus the role the data plays ('usable as a rule's macro instead of proto/port'). This separates it from rule-creation tools, but it never names sibling list tools such as firewall aliases or ipsets, so an agent must infer the distinction from the resource name alone.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'instead of proto/port' clause implies the reason to call this tool (discovering valid macro values for a firewall rule), but there is no explicit when-to-use or when-not framing and no mention of alternatives like proxmox_list_firewall_aliases or proxmox_list_firewall_ipsets. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools