YesTechie — UniFi Network & Security Integrator

List prices

get_pricing

Catalog list prices (USD, pre-tax, before scope): equipment (MSRP) or labor (standard rates). Use when the person asks what one item or labor task costs; use unifi_estimate for a whole project. (REST: GET /api/agent/v0/pricing/{equipment|labor})

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": {
      "kind": "<kind>"
    },
    "name": "get_pricing"
  }
}

Input Schema

Name	Required	Description
`q`	No
`kind`	Yes
`page`	No
`limit`	No
`detail`	No
`fields`	No	Comma-separated field names
`category`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/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 adds useful context such as USD/pre-tax pricing and the REST GET endpoint, which implies a read-only lookup, but it does not disclose pagination behavior, auth requirements, rate limits, or response shape.

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?

The description is compact and front-loaded: pricing scope first, then usage guidance, then endpoint reference. Every sentence adds useful information without repetition.

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?

It gives strong purpose and usage context, but with seven parameters, no annotations, no output schema, and only 14% schema description coverage, an agent still lacks guidance on how to use q, category, pagination, and detail. This is adequate for tool selection but incomplete for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 14%, and the description only explains the kind parameter's meaning (equipment MSRP vs. labor standard rates). It leaves q, page, limit, detail, and category undocumented, so it does not compensate for the low schema coverage.

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: catalog list prices for equipment and labor. It clarifies the pricing basis (USD, pre-tax, before scope) and explicitly distinguishes this tool from unifi_estimate, so an agent can identify its role without 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit selection guidance: use when the person asks what one item or labor task costs, and use unifi_estimate for a whole project. The alternative tool and the condition that selects it are named directly.

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?