Skip to main content
Glama

List MCLAG domains

unifi_net_list_mclag_domains
Read-onlyIdempotent

Lists MCLAG domains configured on the current site to inspect network redundancy groups, with pagination and filter support.

Instructions

MCLAG domains 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_mclag_domains"
  }
}

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

C2.5/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered elsewhere. The description's only added behavioral fact is site scoping ('current site'); it says nothing about result volume, pagination defaults, or what the vendor filter expression applies to.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence fragment with nothing wasted, but it is under-specified rather than well-compressed. It is front-loaded and easy to parse, yet the absence of a verb and any usage framing makes it feel like a title echo.

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?

With no output schema, the description should convey at least the shape or scope of returned data (e.g., that each entry has an ID usable with the get tool). It also omits any note on paging through large MCLAG domain lists, leaving meaningful gaps for a listing tool.

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?

All three parameters (limit, filter, offset) are fully documented in the schema at 100% coverage, so the schema does the heavy lifting. The description adds no additional meaning about how filter interacts with the list or how pagination behaves, which is the baseline case for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (MCLAG domains) and adds a scope qualifier ('configured on the current site'), which is more than a bare restatement of the title. However, the verb is only implied by the tool name rather than stated ('list all' / 'retrieve'), and it does not distinguish itself from unifi_net_get_mclag_domain or unifi_gen_getmclagdomainpage.

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 pick this list tool over the single-domain sibling unifi_net_get_mclag_domain, nor any mention of pagination or filtering strategy. The only implicit cue is that this is a collection-level read, which an agent could infer from the name alone.

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