YesTechie — UniFi Network & Security Integrator

Services

list_services

Published YesTechie services (what we install and operate). Use when the person asks what YesTechie does or whether it offers a service. Lean list (id, slug, url, title, summary, date; page/limit/fields/detail), or one item in full with idOrSlug. (REST: GET /api/agent/v0/services[/{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_services"
  }
}

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.8/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that only published services are returned and that the list is lean versus full-detail for one item, but it does not mention auth requirements, error behavior when idOrSlug is not found, or pagination defaults.

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 use case, then compactly covers list mode, single-item mode, and the REST endpoint. It is dense but every clause serves a purpose; no redundant sentences.

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 read-only list tool with no annotations and no output schema, the description covers the core operation and parameter names reasonably well. However, with only 20% schema description coverage and five parameters, it leaves gaps around pagination semantics, detail mode requirements, and error handling that an agent might need.

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%, so the description must compensate. It names page, limit, fields, detail, and idOrSlug, and explains the list-vs-single-item mode, but it does not clarify parameter meanings such as detail='full' requiring idOrSlug, default page/limit values, or the idOrSlug format.

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 resource (published YesTechie services) and its scope (what YesTechie installs and operates). It also distinguishes the lean list mode from the single-item full-detail mode using idOrSlug, so an agent can understand what the tool does before opening the 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 gives a clear trigger condition: 'Use when the person asks what YesTechie does or whether it offers a service.' That is useful routing guidance, but it does not explicitly compare against the sibling get_service tool, even though both can return a single service via 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?