Skip to main content
Glama

List local DNS records

unifi_list_dns_records
Read-only

Lists a UniFi gateway's local DNS records (A, AAAA, CNAME, MX, TXT, SRV, NS) with name, value, TTL, and enabled state so you can audit or troubleshoot local DNS entries.

Instructions

List the gateway's local DNS records (A, AAAA, CNAME, MX, TXT, SRV, NS) with name, value, TTL and enabled state. Network 8.2+ (v2 static-dns). For a public hostname that follows the WAN IP use unifi_list_dynamic_dns.

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

Input Schema

NameRequiredDescriptionDefault
siteNoSite name/ID as used in the API (e.g. 'default'). Defaults to the configured site. See unifi_list_sites.
fieldsNoOnly return these fields per item (dot paths, e.g. uplink.name)
searchNoCase-insensitive substring match on names, MACs, IPs and similar

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.9.1
    • addedInput schema / properties / fields / description
      Added value: +"Only return these fields per item (dot paths, e.g. uplink.name)"
    • addedInput schema / properties / search / description
      Added value: +"Case-insensitive substring match on names, MACs, IPs and similar"
  2. First observedv0.8.1

TDQS

A4.4/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 the safety profile is covered; the description adds a real constraint beyond them by pinning the required controller version ('Network 8.2+, v2 static-dns'), which tells an agent when the call may fail or be unavailable. It also discloses the shape of what comes back (TTL and enabled state per record). It does not mention pagination, result limits, or auth requirements, keeping it short of a 5.

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, no filler: the first states what is returned and its shape, the second gives the version gate and the disambiguation. The disambiguating routing sentence is placed last where it is most useful.

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, the description compensates by enumerating returned fields and value types, and it flags the version prerequisite. Minor gaps remain around result size/pagination and whether filtering via search follows the same field set, but nothing that would cause an agent to call it incorrectly.

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 site, fields, and search are already documented (including the pointer to unifi_list_sites for site names). The description adds no parameter meaning of its own, so the baseline of 3 applies.

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?

Specific verb and resource ('List the gateway's local DNS records') plus an enumeration of record types (A, AAAA, CNAME, MX, TXT, SRV, NS) and the fields returned (name, value, TTL, enabled state). It also distinguishes itself from the sibling it could be confused with, unifi_list_dynamic_dns.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this for local/static DNS records, and use unifi_list_dynamic_dns when the record is a public hostname that follows the WAN IP. That is a concrete alternative plus the condition that selects it, not just implied usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.