teamspeak3-mcp

client_kick

Remove a client from a TeamSpeak 3 server or current channel by specifying the client ID and an optional reason.

Instructions

Kick a client from the server or current channel

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": {
      "client_id": "<client_id>"
    },
    "name": "client_kick"
  }
}

Input Schema

Name	Required	Description	Default
`reason`	No	Kick reason	Kicked by AI
`client_id`	Yes	Client ID
`from_server`	No	true = kick from server, false = kick from channel

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a destructive action ('Kick') but does not cover permissions required, whether the kick is reversible, what happens to the client, or the effect on other users. This is a significant gap for a moderation tool.

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 a single, front-loaded sentence that efficiently communicates the core action and scope without any wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a moderation tool with no annotations, no output schema, and destructive implications, the description is incomplete. It lacks critical behavioral context such as required permissions, consequences of kicking, and differentiation from related tools like client_ban.

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% (all three parameters have descriptions), so the baseline is 3. The description adds no parameter details beyond the schema, which already documents client_id, reason, and from_server with defaults and meanings.

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 ('Kick') and resource ('a client') with scope ('from the server or current channel'), clearly distinguishing it from siblings like client_ban and client_poke. An agent can immediately understand the tool's action without ambiguity.

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?

The description implies usage by specifying the optional scope (server vs. channel), but does not explicitly state when to use this tool versus alternatives like client_ban or client_move. No exclusions or preconditions are mentioned, leaving the agent to infer context.

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