Skip to main content
Glama

server_start

Start a Minecraft server by providing its ID or UUID to initiate gameplay sessions.

Instructions

Start a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The handler implementation for the tools, including "server_start". It uses the client to perform a post request to the server action endpoint.
    server.tool(
      name,
      description,
      serverIdSchema,
      async ({ server_id }) => {
        try {
          const data = await client.post(`/servers/${server_id}/action/${action}`);
          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 };
        }
      }
    );
  • Registration of the "server_start" tool action mapping.
    const actions: Array<{ name: string; action: string; description: string }> = [
      { name: "server_start", action: "start_server", description: "Start a Minecraft server" },
      { name: "server_stop", action: "stop_server", description: "Stop a Minecraft server (sends configured stop command)" },
      { name: "server_restart", action: "restart_server", description: "Restart a Minecraft server" },
      { name: "server_kill", action: "kill_server", description: "Force-kill a Minecraft server process immediately" },
      { name: "server_backup", action: "backup_server", description: "Trigger an immediate backup of a Minecraft server's files" },
      { name: "server_update_executable", action: "update_executable", description: "Update the server jar/executable from the configured download URL" },
      { name: "server_clone", action: "clone_server", description: "Clone an existing Minecraft server (server must not be running)" },
    ];
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Start a Minecraft server' implies a state-changing operation, but the description doesn't mention permissions required, whether this is synchronous/asynchronous, what happens if the server is already running, or any rate limits. This leaves significant behavioral gaps for a mutation tool.

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?

The description is a single, direct sentence with zero wasted words. It's appropriately sized for a simple tool and front-loads the essential information immediately. Every word earns its place in conveying the core functionality.

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?

For a mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'starting' entails operationally, what the expected outcome is, error conditions, or how this differs from similar sibling tools. Given the complexity of server management and the rich sibling toolset, more contextual information would be helpful.

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%, with the single parameter 'server_id' documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, which is acceptable given the high schema coverage. The baseline score of 3 reflects adequate but minimal value addition.

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 action ('Start') and resource ('a Minecraft server'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'server_restart' or 'server_run_task', which could involve similar server activation scenarios.

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 is provided about when to use this tool versus alternatives like 'server_restart' or 'server_run_task'. The description doesn't mention prerequisites (e.g., server must be stopped), exclusions, or contextual constraints, leaving the agent to infer usage from the tool name alone.

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