Skip to main content
Glama

start_server

Start a Minecraft Java Edition server with RCON enabled and wait for full initialization. Accepts the EULA on first run to begin server operation.

Instructions

Start the Minecraft Java Edition server. Ensures RCON is enabled and waits for startup completion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accept_eulaNoSet to true to accept the Minecraft EULA (https://aka.ms/MinecraftEULA). Required on first run.

Implementation Reference

  • Registration and handler implementation for the start_server tool.
    server.tool(
      "start_server",
      "Start the Minecraft Java Edition server. Ensures RCON is enabled and waits for startup completion.",
      {
        accept_eula: z
          .boolean()
          .optional()
          .describe(
            "Set to true to accept the Minecraft EULA (https://aka.ms/MinecraftEULA). Required on first run."
          ),
      },
      async ({ accept_eula }) => {
        if (accept_eula) {
          manager.acceptEula();
        }
        const result = await manager.start();
        return { content: [{ type: "text", text: result }] };
      }
    );
Behavior4/5

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

With no annotations provided, the description carries the full burden and successfully discloses two key behavioral traits: RCON configuration side effects ('Ensures RCON is enabled') and blocking/sync nature ('waits for startup completion'). However, it omits idempotency details (what happens if server is already running) and error conditions.

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 sentences with zero waste. The primary action is front-loaded ('Start...'), followed by behavioral modifiers. Every word serves the definition.

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

Completeness4/5

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

Given the single parameter and lack of output schema, the description adequately covers the operation's purpose and side effects. A mention of prerequisites or failure modes (e.g., port conflicts) would complete it, but the current content is sufficient for invocation.

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 the accept_eula parameter fully documented. The description doesn't redundantly describe the parameter, which is acceptable when the schema carries the load. Baseline score applies.

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 opens with a specific verb ('Start') and resource ('Minecraft Java Edition server'), clearly distinguishing it from sibling tools like restart_server, stop_server, and setup_world. It specifies the exact edition (Java) to avoid confusion with Bedrock.

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?

The phrase 'waits for startup completion' provides important usage context that this is a blocking operation, but the description lacks explicit contrast with restart_server or prerequisites (e.g., whether setup_world must be run first).

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