Skip to main content
Glama

YesTechie — UniFi Network & Security Integrator

Coverage

get_coverage

Check whether YesTechie serves a location: California HQ, deployments by state and city, travel policy. Use when the person asks if YesTechie works in their area, or before quoting a site outside California. (REST: GET /api/agent/v0/coverage)

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

Input Schema

NameRequiredDescriptionDefault
detailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the burden and does reasonably well: the REST GET notation signals a read-only, side-effect-free call, and the listed contents (HQ, deployments, travel policy) tell the agent what the response covers. It omits what an uncovered location looks like, but for a simple lookup that is a minor gap.

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?

Two front-loaded sentences covering purpose, contents, and when-to-use, plus a short REST endpoint note. No filler; the trailing endpoint parenthetical is marginal but cheap.

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?

No output schema and no annotations, so the description must define what comes back — it does so by naming HQ, deployments, and travel policy. Only the undocumented `detail` parameter keeps it from being fully self-contained.

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?

The single optional `detail` parameter is never mentioned in the description and has 0% schema description coverage. It is mitigated by being optional with a one-value enum ("full"), so an agent can safely omit it, but the description adds nothing here.

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?

States a specific verb and resource ("Check whether YesTechie serves a location") and enumerates the data returned: HQ location, deployments by state/city, travel policy. That enumeration also distinguishes it from look-alikes such as get_site_info or get_contact_info.

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 two concrete triggering conditions: a user asking whether YesTechie works in their area, and a pre-quote check for sites outside California. Clear usage context, though it does not explicitly name a sibling to prefer instead in adjacent cases.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources