Skip to main content
Glama

Get a guest's firewall status

proxmox_get_guest_firewall_status
Read-only

Get a VM/container's firewall status across datacenter, node, guest and NIC levels—policies, rules, IP/MAC filters, and blocking findings—to diagnose unreachable guests.

Instructions

Whole-picture firewall view for one VM/container, for questions like 'why can't I reach VM X': whether the firewall is enabled at datacenter, node and guest level and on each NIC (firewall=1), the effective policies, the guest's rules (one line each), IP/MAC filters, and plain-language findings about what is blocking or not filtering traffic.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vmid": "<vmid>"
    },
    "name": "proxmox_get_guest_firewall_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNoNode the guest is on. Looked up automatically from the VMID when omitted.
vmidYesVM or container ID (VMID), e.g. 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, non-open-world), and the description goes well beyond them by enumerating the returned sections: enablement at three levels plus per-NIC, effective policies, per-rule one-liners, IP/MAC filters, and plain-language blocking findings. It does not discuss response size, error cases, or whether the auto node lookup can fail.

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?

A single sentence with the purpose front-loaded and each clause adding distinct information (scope, motivating question, contents, findings). It is dense but readable; the trailing evidence list is long, though every item is substantive rather than filler.

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?

With no output schema and only two parameters, the description carries the return-value burden and does so by enumerating the included sections, letting an agent decide it doesn't need the per-level firewall tools. Missing only peripheral detail such as output size or how findings are phrased.

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%, with both `node` and `vmid` fully documented including the auto-lookup fallback, so the description adds little beyond restating 'one VM/container'. The mention of `firewall=1` refers to Proxmox config values, not to an input 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 names a specific resource (one guest's firewall status) and frames it as an aggregate 'whole-picture' view spanning datacenter, node, guest, and per-NIC enablement plus rules and filters. That aggregation framing implicitly distinguishes it from the narrower firewall siblings (options, rules, log), though no sibling is named explicitly.

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?

It gives a concrete situational trigger -- diagnosing 'why can't I reach VM X' -- which tells an agent exactly when to reach for this tool. It does not state when to prefer the narrower tools (e.g. firewall log or options) once an agent already knows the level it cares about.

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