Skip to main content
Glama

server_stop

Stop a Minecraft server by sending the configured stop command using its server ID. This tool helps manage server operations within the crafty-mcp environment.

Instructions

Stop a Minecraft server (sends configured stop command)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The `registerServerActionTools` function iterates over an array of action definitions, including `server_stop`, and registers them as MCP tools using `server.tool`. The handler logic for all these actions, including `server_stop`, is defined within the `async ({ server_id }) => { ... }` function block, which calls the Crafty API.
    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?

No annotations are provided, so the description carries the full burden. It discloses that the tool sends a configured stop command, hinting at graceful shutdown behavior, but fails to mention critical details like required permissions, whether it's destructive (likely yes, as it stops a server), rate limits, or what happens if the server is already stopped. This leaves significant gaps in behavioral understanding.

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 that front-loads the core action ('Stop a Minecraft server') and adds necessary clarification ('sends configured stop command') without any wasted words. It is appropriately sized for the tool's complexity.

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 no annotations and no output schema, the description is incomplete for a destructive tool. It covers the basic purpose and hints at behavior but lacks details on permissions, effects, error conditions, or return values. For a tool that likely alters server state, more context is needed to ensure safe and correct usage.

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' well-documented in the schema. The description does not add any additional meaning or context about the parameter beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 clearly states the specific action ('Stop') and resource ('a Minecraft server'), and distinguishes it from siblings like 'server_kill' (immediate termination) and 'server_restart' (stop then start) by specifying it sends a configured stop command, indicating a graceful shutdown process.

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 description implies usage context by mentioning 'configured stop command,' suggesting it should be used for normal shutdowns rather than forceful termination (server_kill). However, it lacks explicit guidance on when to use it versus alternatives like server_restart or server_kill, and does not mention prerequisites such as server state or permissions.

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