Skip to main content
Glama
MarlBurroW

TeamSpeak MCP

by MarlBurroW

update_server_settings

Update TeamSpeak virtual server settings such as name, welcome message, max clients, password, host message, and default groups. Modify server configuration to control client limits, access, and introductory messages.

Instructions

Update virtual server settings (name, welcome message, max clients, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoServer name (optional)
welcome_messageNoServer welcome message (optional)
max_clientsNoMaximum number of clients (optional)
passwordNoServer password (optional, empty string to remove)
hostmessageNoHost message displayed in server info (optional)
hostmessage_modeNoHost message mode: 0=none, 1=log, 2=modal, 3=modalquit (optional)
default_server_groupNoDefault server group ID for new clients (optional)
default_channel_groupNoDefault channel group ID for new clients (optional)
Behavior2/5

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

No annotations provided. Description only indicates mutation but omits permission needs, reversibility, or return behavior.

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?

Single, front-loaded sentence. Use of 'etc.' introduces vagueness but overall concise.

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?

Fails to describe output behavior or confirm that all parameters are optional. Incomplete for a tool with 8 optional parameters and no output schema.

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 covers 100% of parameters with descriptions. The tool description adds no new meaning beyond listing examples.

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 clearly states 'Update virtual server settings' with examples, distinguishing it from read-only tools like 'server_info'. However, 'etc.' is imprecise; the schema compensates.

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?

No guidance on when to use this tool versus alternatives. Lacks context on prerequisites or side effects.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/MarlBurroW/teamspeak-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server