TeamSpeak MCP

get_instance_logs

Access TeamSpeak instance-level logs for system-wide monitoring and issue diagnosis. Specify log count, reverse order for newest entries, and optional starting position to narrow down events.

Instructions

Get instance-level logs instead of virtual server logs

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_instance_logs"
  }
}

Input Schema

Name	Required	Description
`lines`	No	Number of log lines to retrieve (1-100, default: 50)
`reverse`	No	Show logs in reverse order (newest first, default: true)
`begin_pos`	No	Starting position in log file (optional)

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 15, 2025

TDQS

A3.6/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 read-only nature, permissions required, or performance impact. The description only restates the tool's function without adding safety or side-effect context.

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 phrase with no unnecessary words. It efficiently conveys the purpose and contrast.

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?

The description does not explain what instance-level logs are, what output format to expect, or the default behavior when no parameters are provided. Given the absence of an output schema, more context is needed for an agent to fully understand the tool's operation.

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 provides complete descriptions for all parameters (100% coverage), so the description adds no additional meaning. Baseline score of 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 tool retrieves instance-level logs and explicitly contrasts with virtual server logs, distinguishing it from the sibling tool view_server_logs.

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

Usage Guidelines4/5

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

The description explicitly says 'instead of virtual server logs,' providing clear guidance on when to use this tool versus its sibling. However, it does not mention any prerequisites or scenarios to avoid.

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