TeamSpeak MCP

kick_client

Kick a client from a TeamSpeak server or channel by specifying their client ID. Optionally provide a reason and choose between server-wide or channel removal.

Instructions

Kick a client from server or 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": "kick_client"
  }
}

Input Schema

Name	Required	Description	Default
`client_id`	Yes	Client ID
`reason`	No	Kick reason	Expelled by AI
`from_server`	No	Kick from server (true) or channel (false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose all behavioral traits. It only states the basic action without explaining consequences (e.g., whether the client is notified, if the kick is reversible, or any permission requirements).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence with no fluff, making it concise. However, it could be better structured by front-loading key information or using bullet points for clarity, though it is not overly verbose.

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?

Given the tool has three parameters, no output schema, no annotations, and exists alongside similar tools like ban_client, the description fails to explain distinctions (e.g., temporary vs permanent), post-kick behavior, or restrictions (e.g., cannot kick self). It is insufficient for full context.

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?

The input schema covers all three parameters with descriptions (100% coverage). The tool description adds minimal extra meaning, mainly implying the scope via 'from server or channel', but does not elaborate on the parameters beyond what the schema already provides.

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 clearly states the action ('Kick') and the resource ('client'), and specifies the two scopes ('from server or channel'), effectively distinguishing it from sibling tools like ban_client or move_client.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool over alternatives (e.g., ban_client), no prerequisites, and no context on when to set the 'from_server' parameter. The default reason is given but not contextualized.

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