Skip to main content
Glama

List firewall policies

unifi_net_list_firewall_policies
Read-onlyIdempotent

Lists all firewall policies for the current site, with optional limit, offset, and filter parameters to page or narrow results.

Instructions

Lists all firewall policies on the current site.

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": "unifi_net_list_firewall_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
filterNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the site-scoping context ('current site'), which is useful, but says nothing about pagination behavior despite the limit/offset parameters, so no real depth beyond annotations.

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, front-loaded sentence with zero filler. It is efficient, though the brevity is under-specification rather than disciplined economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a list tool with no output schema, zero parameter documentation, and a near-identical sibling, one bare sentence is not enough. An agent cannot tell how to page results, what filter syntax is accepted, or why to pick this over the generated counterpart.

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?

Schema description coverage is 0%, so the description must compensate for three undocumented parameters (limit, filter, offset) and it does not mention any of them. Worse, 'Lists all' arguably contradicts the existence of a 'filter' parameter, implying no server-side filtering is possible.

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 states a specific verb and resource ('Lists all firewall policies') plus a scope ('on the current site'), which is enough to know what the tool does. However, it does not distinguish itself from siblings such as unifi_gen_getfirewallpolicies, which appears to expose the same resource, leaving ambiguity.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the apparent duplicate unifi_gen_getfirewallpolicies, nor versus unifi_net_list_firewall_zones or unifi_net_get_firewall_policy. The only implicit signal is 'all' vs the singular get tool.

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