TeamSpeak MCP

deploy_server_snapshot

Restore a TeamSpeak server to a previous state by deploying snapshot data captured from the create_server_snapshot tool.

Instructions

Deploy/restore a server configuration from a snapshot

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": {
      "snapshot_data": "<snapshot_data>"
    },
    "name": "deploy_server_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`snapshot_data`	Yes	Snapshot data to deploy (from create_server_snapshot)

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the deployment is destructive, what happens to the current configuration, or any authorization requirements. This leaves significant behavioral gaps.

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 very short (one sentence) and front-loaded. It is efficient but might be too terse for some users; however, it earns its place with no unnecessary words.

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?

Given the low complexity (1 parameter, no output schema), the description covers the basic purpose but lacks details on behavior, return values, or prerequisites. It is minimally adequate but incomplete.

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 coverage is 100%, and the parameter description 'Snapshot data to deploy (from create_server_snapshot)' is adequate. The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 ('Deploy/restore') and the resource ('server configuration from a snapshot'). It distinguishes from sibling 'create_server_snapshot' which creates snapshots, whereas this deploys them.

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 when you have a snapshot to deploy, but it does not provide explicit guidance on when to use this tool vs alternatives (e.g., when not to use it, prerequisites).

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