YesTechie — UniFi Network & Security Integrator

Team

get_team

Published founders (list), or one founder in full with idOrSlug. Use when the person asks who runs YesTechie. (REST: GET /api/agent/v0/team[/{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": "get_team"
  }
}

Input Schema

Name	Required	Description
`detail`	No
`fields`	No	Comma-separated field names
`idOrSlug`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that this is a REST GET endpoint, that only published founders are returned, and that idOrSlug switches to a full single-founder response, but it omits auth requirements, pagination behavior, and response shape details.

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 definition is compact and front-loaded: it states the main return modes first, then the usage trigger, then the REST endpoint in parentheses. Every element adds useful context without unnecessary prose.

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?

There are no annotations and no output schema, and schema description coverage is low. The description covers the core purpose and the idOrSlug variant, but it leaves gaps around the fields parameter, the detail enum, auth requirements, and what fields a returned founder includes.

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 33%, so the description needs to compensate. It explains that idOrSlug retrieves one founder in full and implies list behavior when omitted, but it does not explain the fields parameter or clarify the detail=full enum beyond the phrase 'in full'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and two return modes: published founders as a list, or one founder in full when idOrSlug is provided. It also ties the tool to the concrete user intent of asking who runs YesTechie, but it does not explicitly differentiate itself from sibling tools such as get_join_our_team.

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 usage trigger: use this when the person asks who runs YesTechie. It does not provide exclusions, alternatives, or guidance on when to request the detailed single-founder form versus the list form.

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?