Skip to main content
Glama

restart_server

Restart the Minecraft server to apply configuration changes or resolve issues by stopping and starting the server process.

Instructions

Restart the Minecraft server (stop then start). Useful after configuration changes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The 'restart' method in ServerManager stops and then starts the server.
    /** Restart the server */
    async restart(): Promise<string> {
      const stopResult = await this.stop();
      // Wait a moment for cleanup
      await new Promise((r) => setTimeout(r, 2000));
      const startResult = await this.start();
      return `Stop: ${stopResult}\nStart: ${startResult}`;
    }
  • The 'restart_server' MCP tool is registered here, which calls the manager.restart() method.
    // --- Restart Server ---
    server.tool(
      "restart_server",
      "Restart the Minecraft server (stop then start). Useful after configuration changes.",
      {},
      async () => {
        const result = await manager.restart();
        return { content: [{ type: "text", text: result }] };
      }
    );
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the sequential nature (stop then start) and implies configuration changes require restart to take effect. However, lacks critical behavioral details: downtime duration, graceful vs. forceful termination, prerequisites (server must be running?), and error handling if already stopped.

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 compact sentences with zero redundancy. First sentence defines the operation, second provides usage context. Front-loaded with the most critical information.

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?

Given zero parameters and no output schema or annotations, the description adequately covers the primary happy-path scenario. However, significant gaps remain regarding edge cases (server already stopped, startup failures) and return value expectations, which are critical for a mutation tool without structured safety hints.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema contains zero parameters (empty object). With no parameters to document, baseline score per rubric is 4. Description appropriately focuses on behavior rather than inventing parameter documentation.

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?

Excellent specificity with clear verb (restart), resource (Minecraft server), and mechanism clarification (stop then start). The parenthetical explicitly distinguishes this from siblings start_server and stop_server.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear when-to-use guidance ('Useful after configuration changes'), giving the agent a specific trigger condition. Lacks explicit when-not-to-use guidance or named alternatives, though the mechanism '(stop then start)' implicitly signals not to use for partial operations.

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