YesTechie — UniFi Network & Security Integrator

Articles

list_articles

Practical configuration guides and technical articles: UniFi network, Wi-Fi, cameras (Protect) and access control (Access, Identity, intercom), plus cabling and home networking. One item returns title, summary, author, tags, the full step-by-step body, headings and source links. Use when the person asks how to set up, configure or choose UniFi network, Wi-Fi, camera or door-access gear. Lean list (id, slug, url, title, summary, date; page/limit/fields/detail), or one item in full with idOrSlug. (REST: GET /api/agent/v0/articles[/{idOrSlug}])

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

Input Schema

Name	Required	Description
`page`	No
`limit`	No
`detail`	No
`fields`	No	Comma-separated field names
`idOrSlug`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden and does good work: it enumerates the returned item fields (title, summary, author, tags, full step-by-step body, headings, source links) and distinguishes the lean-list payload from the full item. It omits pagination defaults/limits and the REST path is noted, but overall behavioral disclosure is solid.

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?

Dense but front-loaded: scope, return shape, trigger, then mode/parameter hints. The topical enumeration is a bit long but each clause adds selection signal; nothing is pure filler.

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 5 optional params, no annotations and no output schema, the description supplies the return-field inventory and both access modes, which is most of what an agent needs. The remaining gap is the ambiguous `detail` interaction and pagination behavior, which are not fully resolvable from the schema.

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 only 20% (only `fields` is documented), so the description must compensate. It names page/limit/fields/detail and binds idOrSlug to the single-item mode, but leaves detail's semantics ambiguous (does it apply to the list or only with idOrSlug?) and doesn't explain fields syntax, limit bounds, or defaults.

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?

Opens with a specific resource (practical configuration guides/articles on UniFi network, Wi-Fi, Protect, Access, cabling) and a specific verb (list). It separates the lean-list and single-item return modes, though it never names the sibling get_article that overlaps with the idOrSlug mode.

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?

Gives an explicit trigger: 'Use when the person asks how to set up, configure or choose UniFi... gear.' It also explains the list-vs-one-item choice, but offers no exclusion telling the agent when get_article (single fetch) is preferable over this tool with idOrSlug.

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

All YesTechie — UniFi Network & Security Integrator tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?