Skip to main content
Glama

server_logs

Retrieve recent console output from a Minecraft server to debug startup issues or monitor server activity. Specify the number of log lines to fetch.

Instructions

Get recent server console output. Useful for debugging startup issues or monitoring activity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linesNoNumber of recent log lines to retrieve (default: 50, max: 500)

Implementation Reference

  • The 'server_logs' tool is registered and implemented in src/tools/server-tools.ts. It uses the ServerManager instance to fetch recent logs and returns them as text content.
    server.tool(
      "server_logs",
      "Get recent server console output. Useful for debugging startup issues or monitoring activity.",
      {
        lines: z
          .number()
          .optional()
          .default(50)
          .describe("Number of recent log lines to retrieve (default: 50, max: 500)"),
      },
      async ({ lines }) => {
        const count = Math.min(Math.max(1, lines), 500);
        const output = manager.getRecentOutput(count);
        if (output.length === 0) {
          return {
            content: [
              {
                type: "text",
                text: "No server output available. The server may not have been started.",
              },
            ],
          };
        }
        return { content: [{ type: "text", text: output.join("\n") }] };
      }
    );
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. Words 'Get' and 'monitoring' imply read-only safety, but description does not explicitly confirm this is non-destructive, disclose return format (string vs array), or mention if logs are consumed/cleared upon retrieval.

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?

Two efficient sentences. First states action and resource, second provides use-case context. No repetition of name/tautology, no extraneous 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?

Adequate for a simple single-parameter tool, but lacks compensation for missing output schema (return format unspecified) and missing annotations (safety characteristics not confirmed). Description could explicitly state this retrieves without modifying server state.

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% (lines parameter fully documented with constraints). Description does not add parameter semantics beyond schema, but baseline 3 is appropriate given schema completeness.

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 specific verb ('Get') and resource ('server console output') clearly. Mentions 'recent' implying scoping. However, does not explicitly distinguish from siblings like 'execute_command' which also returns output, or clarify relationship to 'server_status'.

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?

Provides implied usage context via 'Useful for debugging startup issues or monitoring activity,' indicating when to use. However, lacks explicit when-not guidance, prerequisites (e.g., server must be running?), or named alternatives for different log retrieval scenarios.

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/tamo2918/Minecraft-Server-MCP'

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