Skip to main content
Glama

List DNS policies

unifi_net_list_dns_policies
Read-onlyIdempotent

Lists all DNS policies configured on the current UniFi site, with optional filtering and pagination to review or audit site-level DNS rules.

Instructions

Lists all DNS policies configured 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_dns_policies"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, at most 200 (vendor default applies when unset)
filterNoVendor filter expression
offsetNoNumber of items to skip (vendor default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld behavior, so the description's only added context is site scoping. It says nothing about pagination limits, result ordering, or whether the list is truncated by the limit parameter despite exposing limit/offset.

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?

One short sentence with the scope front-loaded and no wasted words. It is appropriately sized, though it is arguably under-specified rather than genuinely well-structured.

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

Completeness3/5

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

For a simple paginated list tool with full annotation coverage and complete parameter docs, the description is minimally sufficient. It still omits paging mechanics and any note on what a DNS policy record contains, and there is no output schema to fall back on.

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 description coverage is 100%, so limit, filter and offset are fully documented in the schema (including a max of 200 and vendor defaults). The description adds no extra meaning about filter expression syntax or how paging interacts with the site scope, so baseline 3 applies.

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 ("Lists all DNS policies") and scopes it to the current site, which distinguishes it from unifi_net_get_dns_policy by plurality implied through the name. It never explicitly contrasts with the singular getter, so it stops short of 5.

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 versus unifi_net_get_dns_policy or the generated unifi_gen_getdnspolicypage alternative, and nothing about prerequisites or paging strategy. The single sentence gives implied usage from the name only.

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