YesTechie — UniFi Network & Security Integrator

Contact YesTechie

submit_contact

Request a site survey or callback. Attach quoteRef. Use when the person explicitly asks to be contacted and has supplied name and email or phone; it sends a real email. 3 per IP and 2 per email per day. (REST: POST /api/agent/v0/contact)

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": {
      "fullName": "<fullName>",
      "email": "<email>",
      "message": "<message>"
    },
    "name": "submit_contact"
  }
}

Input Schema

Name	Required	Description
`email`	Yes
`phone`	No
`message`	Yes
`fullName`	Yes
`quoteRef`	No	Optional: the quoteRef from get_quote / unifi_estimate (valid 24 h). Attaches that estimate to the request.
`organization`	No
`idempotencyKey`	No	Sent as the Idempotency-Key header (retry safely)

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that a real email is sent, and gives concrete rate limits ('3 per IP and 2 per email per day'), which the agent cannot infer from the schema. It omits reversibility and what a successful submission returns, which is the remaining gap.

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?

Four short sentences, front-loaded with purpose, then attachment, eligibility gate, side effect and limits, with the REST route in a trailing parenthetical. No sentence is redundant.

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 mutation tool with no annotations and no output schema, the description covers the critical facts: side effect (real email), rate limits, and eligibility. It would be complete with a note on what success looks like and confirmation of whether `message` content is free-form.

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 only 29%, so the description must compensate, and it only partially does: it explains quoteRef attachment and the name/email/phone requirement. It says nothing about `message`, `organization`, or the retry semantics of `idempotencyKey`, and 'email or phone' is slightly at odds with the schema requiring `email`. Adequate but incomplete.

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 action and resource: 'Request a site survey or callback' with an attached quoteRef. This is clearly distinct from the read-only siblings (get_contact_info, get_about) and from submit_join_application. An agent can identify what it does and what it does not do 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 Guidelines4/5

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

'Use when the person explicitly asks to be contacted and has supplied name and email or phone' gives an explicit precondition that gates the call. It does not name an alternative path (e.g. get_contact_info for mere contact lookups), but the user-intent gate is a strong, actionable constraint.

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?