Skip to main content
Glama

Get firewall options

proxmox_get_firewall_options
Read-only

Retrieve Proxmox firewall options for a datacenter, node, or guest, including enablement, default policies, and protection settings; use effective to fill in unset defaults.

Instructions

Get firewall options for the datacenter (enable, default policies, ebtables, log rate limit), a node (enable, nftables, conntrack, synflood/smurf/tcpflags protection, log levels) or a guest (enable, policies, MAC/IP filter, DHCP, NDP, RA, log levels). effective fills in Proxmox's defaults for unset options.

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_get_firewall_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode name: the host for scope node (defaults to PROXMOX_DEFAULT_NODE or the only node), or the guest's node for scope guest (looked up from vmid when omitted)
vmidNoVM or container ID, for scope guest
scopeNoFirewall level: cluster = datacenter-wide; node = a host's own firewall; guest = a VM or container (give vmid). Inferred when omitted: guest if vmid is given, node if node is given, otherwise cluster.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/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 externally. The description adds one genuinely useful behavioral fact — that `effective` substitutes Proxmox's defaults for unset options — but says nothing about error behavior or response shape beyond field names.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then a tight parenthetical enumeration per scope, plus a single second sentence on `effective`. The field lists are long but each item earns its place by telling the agent what comes back.

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 read-only getter with full schema coverage and no output schema, the description usefully compensates by enumerating the returned option fields per scope. The only gaps are the unexplained `effective` input (absent from the schema) and no indication of response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so node/vmid/scope semantics (including scope inference) are already documented in the schema, establishing the baseline of 3. The description contributes scope-to-field mapping and explains `effective`, but `effective` is not present in the input schema, which creates a small mismatch rather than added clarity for a real parameter.

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?

The description opens with a specific verb+resource ("Get firewall options") and then enumerates the three scopes it covers, naming the actual option fields returned at each level (policies, ebtables, conntrack, MAC/IP filter, etc.). That gives an agent a precise picture of what is retrieved and separates it from generic cluster/option getters, though it never names a sibling alternative.

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?

The three scope descriptions make it clear which scope to pick for a datacenter-wide, host-level, or VM/CT-level query, and the note about `effective` signals when to use it to resolve unset defaults. There are no explicit when-not conditions or named alternatives, so it falls short of full routing guidance.

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