Skip to main content
Glama

Read the server log

server_logs
Read-onlyIdempotent

Retrieve the latest Minecraft server log lines, including console output when startup fails, and filter them by text to diagnose errors and monitor server activity.

Instructions

The last lines of the server log (logs/latest.log), or of the console output if the server failed to start. Optional filter keeps only lines containing that text. The RCON password is hidden.

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": "server_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
linesNoHow many lines. Default 80.
filterNoOnly lines containing this text (not case sensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, yet the description still adds real behavior: it returns a tail rather than the whole file, it switches source on startup failure, and it redacts the RCON password. That redaction note is meaningful because the agent now knows it can paste output without leaking credentials. It stops short of describing ordering or truncation behavior, so not a 5.

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?

Three short sentences, each earning its place: source and scope first, filter second, redaction guarantee last. No preamble, no repetition, and the most load-bearing fact (what file, how much) is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-optional-parameter read tool with rich annotations and no output schema, the description covers the source, the fallback path, the tail semantics, the filter, and the redaction guarantee. Nothing an agent needs in order to call it correctly and interpret the result is missing.

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%, with both parameters documented including default, min/max and case-insensitivity, so the baseline is 3. The description only adds that 'lines' means the trailing N lines rather than an offset or page size, and otherwise restates the filter semantics already in the schema.

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?

States the specific resource and scope precisely: 'the last lines of the server log (logs/latest.log)', plus a fallback source (console output when the server failed to start). The only gap is that it never distinguishes itself from the sibling read_file/list_files, which could also target that path.

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?

Usage is implied by the fallback clause ('or of the console output if the server failed to start'), which tells the agent this tool remains useful after a crash. There is no explicit when-to-use-vs-alternatives guidance and no stated prerequisites, so the reader must infer the routing.

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