Skip to main content
Glama

List firewall security groups

proxmox_list_firewall_groups
Read-only

List Proxmox VE datacenter firewall security groups, including comments and rule counts, so you can review and select reusable rule sets.

Instructions

List the datacenter's security groups (reusable rule sets) with their comment and rule count. See a group's rules with proxmox_list_firewall_rules scope=group; apply a group to a guest/node with a rule of type group.

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

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real value by disclosing the shape of each entry (comment and rule count), which matters because there is no output schema. It stops short of pagination, ordering, or result-size behavior, and the idempotentHint=false on a read-only list goes unaddressed.

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?

Two sentences, both earning their place: the first defines the resource and its returned fields, the second routes the agent to the related tools. Return shape is front-loaded before the cross-references.

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 read-only list tool with no output schema, the description covers purpose, returned content, and follow-on tools. The remaining gap is the unexplained `fields` parameter and no note on ordering or result limits.

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?

With 2 parameters at 50% schema coverage, the description never mentions either parameter. The schema documents `search` as a case-insensitive substring filter, but `fields` is undocumented in both the schema and the description, so the description does not compensate for the gap.

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?

Uses a specific verb plus resource ("List the datacenter's security groups") and immediately disambiguates with the parenthetical "(reusable rule sets)", then states what is returned: comment and rule count. It also separates this tool from proxmox_list_firewall_rules by noting that tool returns a group's rules.

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 second sentence gives clear routing context: use proxmox_list_firewall_rules with scope=group for rules, and apply a group via a rule of type group. That's helpful next-step guidance, but there is no explicit when-not or statement of which scenario requires listing groups first.

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