Skip to main content
Glama
MarlBurroW

TeamSpeak MCP

by MarlBurroW

view_server_logs

Retrieve recent log entries from a TeamSpeak virtual server with options to filter by log level, timestamp range, line count, and order. Supports instance logs and automatic pagination for complete retrieval.

Instructions

View recent entries from the virtual server log with enhanced options

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNoNumber of log lines to retrieve (1-100, default: 50)
reverseNoShow logs in reverse order (newest first, default: true)
instance_logNoShow instance log instead of virtual server log (default: false)
begin_posNoStarting position in log file (optional)
log_levelNoLog level (1=ERROR, 2=WARNING, 3=DEBUG, 4=INFO)
timestamp_fromNoUnix timestamp for log entries from (optional)
timestamp_toNoUnix timestamp for log entries to (optional)
complete_modeNoEnable complete mode - retrieve ALL logs by paginating automatically (default: false)
max_iterationsNoMaximum pagination iterations in complete mode (default: 1000, protection against infinite loops)
enhanced_debugNoEnable enhanced debugging information (default: false)
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to mention any safety traits, rate limits, or side effects. The phrase 'enhanced options' is vague and does not clarify behavior beyond filtering.

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

Conciseness3/5

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

The description is a single sentence: concise but overly brief. It lacks structure and does not front-load critical information. It is not verbose but could be more informative without adding length.

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 10 parameters and no output schema, the description is very incomplete. It does not explain the return format, pagination behavior, or how log levels work, even though some details are in the schema. The tool's complexity warrants more 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add any additional meaning beyond what the schema provides for each parameter.

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 the verb 'View' and the resource 'virtual server log entries'. It mentions 'enhanced options' hinting at additional parameters, but does not explicitly differentiate from the sibling tool 'get_instance_logs'.

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 versus alternatives like 'get_instance_logs' or 'add_log_entry'. There are no explicit usage conditions or exclusions.

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