teamspeak3-mcp

server_search

Search online TeamSpeak 3 clients by name/UID or channels by name pattern to support AI-driven client and channel management.

Instructions

Search for online clients by name/UID or channels by name pattern

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": {
      "type": "<type>",
      "pattern": "<pattern>"
    },
    "name": "server_search"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Search type
`by_uid`	No	Search clients by unique identifier instead of name (only for type=client)
`pattern`	Yes	Search pattern (name or UID)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 13, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the full burden. It does disclose one real behavioral trait, that only *online* clients are matchable, but says nothing about permissions, result limits, or return shape, which is significant for a query tool with no output schema.

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?

A single front-loaded sentence with no filler; every word maps to a searchable dimension of the tool.

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?

For a parameterized search tool with no annotations and no output schema, the definition is adequate but thin: it does not hint at the result format, pagination, or whether results are capped, leaving the agent to discover return behavior empirically.

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 100%, so the schema already documents type, by_uid, and pattern. The description broadly mirrors this (name/UID, channel name pattern) without adding syntax or format detail beyond it, so baseline 3 applies.

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?

States a specific verb (Search) and resource (online clients / channels) with the two searchable axes (name/UID vs name pattern). It is clearly distinguishable from siblings like server_list or client_info, though it does not name a sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer this is the lookup tool for clients/channels, and 'online clients' quietly scopes the target set. There is no explicit when-to-use, when-not-to-use, or named alternative.

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