Skip to main content
Glama

server_restart

Restart a Minecraft server by providing its server ID or UUID to apply changes or resolve issues.

Instructions

Restart a Minecraft server

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The 'server_restart' tool is registered as part of a loop in 'registerServerActionTools'. It uses a generic handler that executes a POST request to the Crafty API using the 'restart_server' action.
    export function registerServerActionTools(server: McpServer, client: CraftyClient): void {
      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)" },
      ];
    
      for (const { name, action, description } of actions) {
        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 };
            }
          }
        );
      }
    }
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose whether this requires specific permissions, if it's destructive (interrupts gameplay), what happens during restart (downtime, save states), or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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, efficient sentence with zero waste—it directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded for quick comprehension.

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 incomplete. It lacks behavioral context (permissions, effects, errors) and output expectations, which are critical for safe agent invocation. The 100% schema coverage helps with parameters but doesn't compensate for missing operational details.

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), so the baseline is 3. The description adds no additional parameter information beyond what the schema provides, but doesn't need to compensate for gaps.

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 ('Restart') and resource ('a Minecraft server'), making the purpose immediately understandable. It distinguishes from siblings like server_start and server_stop by specifying the restart operation, though it 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 is provided on when to use this tool versus alternatives like server_start, server_stop, or server_kill. The description lacks context about prerequisites (e.g., server must be running) or exclusions (e.g., not for initial startup).

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