Skip to main content
Glama

server_get_logs

Retrieve Minecraft server console logs as an array of log lines to monitor server activity and troubleshoot issues. Specify the server ID to access its logs.

Instructions

Get a Minecraft server's console logs as an array of log lines

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The implementation of the server_get_logs tool, which retrieves logs from the CraftyClient.
    server.tool(
      "server_get_logs",
      "Get a Minecraft server's console logs as an array of log lines",
      {
        server_id: z.string().describe("Server ID or UUID"),
      },
      async ({ server_id }) => {
        try {
          const data = await client.get(`/servers/${server_id}/logs`);
          return { content: [{ type: "text", text: JSON.stringify(data, null, 2) }] };
        } catch (error) {
          const msg = error instanceof Error ? error.message : String(error);
          return { content: [{ type: "text", text: `Error: ${msg}` }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the action but lacks behavioral details: no mention of permissions needed, rate limits, whether logs are real-time or historical, pagination, or error conditions. 'Get' implies a read operation, but that's insufficient for a mutation-heavy context with tools like server_delete or server_kill.

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?

Single sentence, front-loaded with the core action, zero waste. Every word contributes to understanding the tool's purpose without redundancy.

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 no annotations, no output schema, and a simple parameter, the description is incomplete. It doesn't explain return format details (e.g., log line structure, timestamps), error handling, or operational context in a server management system with many mutation tools.

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% (server_id parameter is fully documented in schema). The description adds no parameter-specific information beyond what's in the schema, so it meets the baseline of 3 without compensating or adding value.

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 ('Get') and resource ('Minecraft server's console logs'), specifying the output format ('as an array of log lines'). It distinguishes from siblings like server_get (general info) or server_get_stats (metrics), but doesn't explicitly contrast them.

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?

No guidance on when to use this tool versus alternatives like server_get_history or server_get (which might include logs). The description implies it's for retrieving console logs specifically, but doesn't mention prerequisites, timing, 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/HadiCherkaoui/crafty-mcp'

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