YesTechie — UniFi Network & Security Integrator

Service

get_service

One YesTechie service in full: what is included and how it is delivered. Use when the person asks about a specific service (find it with list_services). (REST: GET /api/agent/v0/services/{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_service"
  }
}

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

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It includes the REST endpoint ('GET /api/agent/v0/services/{idOrSlug}'), which implies a read-only operation, but it does not state authentication requirements, rate limits, error behavior, or explicitly confirm the absence of side effects. This is adequate but not rich.

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, front-loaded with the purpose, followed by usage context and a helpful REST reference. Every element earns its place without redundancy.

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 simple single-parameter GET tool with no output schema, the description covers the essential information: what it returns ('in full: what is included and how it is delivered'), when to use it, and how to obtain the ID. It could be slightly more complete by hinting at the return structure or error cases, but it is largely sufficient.

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 schema already documents idOrSlug as 'Numeric id or slug from the list tool'. The description's parenthetical 'find it with list_services' echoes this without adding new semantic detail, so the baseline of 3 is appropriate.

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 ('One YesTechie service in full') and its content ('what is included and how it is delivered'), clearly distinguishing it from the list tool by naming list_services as the place to find the ID. An agent can identify this as a single-resource retrieval tool without ambiguity.

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?

It explicitly states when to use it ('when the person asks about a specific service') and points to the alternative tool for finding the ID ('find it with list_services'). This gives both the condition for use and the prerequisite step, leaving no inference needed.

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?