YesTechie — UniFi Network & Security Integrator

Article

get_article

One practical configuration guide or technical article in full (UniFi network, Wi-Fi, cameras, access control, cabling): title, summary, author, tags, step-by-step body, headings, images and source links. Use when you know which guide answers the person (from list_articles) and need its steps. (REST: GET /api/agent/v0/articles/{idOrSlug})

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "idOrSlug": "<idOrSlug>"
    },
    "name": "get_article"
  }
}

Input Schema

Name	Required	Description	Default
`idOrSlug`	Yes	Numeric id or slug from the list tool

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.9/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the returned content fields (title, summary, author, tags, body, headings, images, source links) and that it is a GET, but it does not state behavior for missing IDs/slugs, auth requirements, or rate limits.

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?

The description is front-loaded with the resource and return contents, then the usage condition and endpoint. It is compact for the amount of information, though the field enumeration is dense and could be slightly tightened.

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?

For a one-parameter read tool with no output schema, the description is largely complete: it explains what full content is returned and when to call it. The main remaining gap is error/missing-record behavior, which is not covered by annotations or an output 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 coverage is 100%, and the single idOrSlug parameter is fully documented in the schema. The description adds only the implied sourcing of the value from list_articles and does not add format or fallback details beyond the schema.

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?

The description states a specific verb and resource: retrieving one configuration guide or technical article 'in full'. It names the sibling tool list_articles as the discovery path, so an agent can distinguish this from listing tools without opening either schema.

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?

It clearly says when to use it: when you already know which guide answers the person (from list_articles) and need its steps. That routes the agent away from list_articles, but it does not mention exclusions or what to do when the guide is unknown or unavailable.

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?