Skip to main content
Glama

server_kill

Force-kill a Minecraft server process immediately using the server ID. This tool terminates unresponsive or problematic servers in the crafty-mcp environment.

Instructions

Force-kill a Minecraft server process immediately

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
server_idYesServer ID or UUID

Implementation Reference

  • The tool 'server_kill' is registered within the 'registerServerActionTools' function. The tool handler uses the 'client.post' method to execute the 'kill_server' action on the server.
    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 full burden. It discloses the destructive nature ('force-kill') and immediacy, but lacks details on permissions required, potential data loss, side effects, or error conditions. For a destructive operation with zero annotation coverage, this is insufficient.

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 wasted words. It front-loads the core action ('Force-kill') and resource, making it immediately understandable without unnecessary elaboration.

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?

Given the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like safety warnings, return values, or error handling, which are critical for a force-kill operation in this context.

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% for the single parameter 'server_id', so the schema already documents it adequately. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline of 3 for high schema coverage.

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 ('Force-kill') and resource ('a Minecraft server process'), and distinguishes it from sibling tools like 'server_stop' or 'server_restart' by emphasizing immediacy. It uses precise language that conveys urgency and finality.

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 through 'force-kill' and 'immediately', suggesting it's for urgent termination, but doesn't explicitly state when to use this versus alternatives like 'server_stop' or 'server_restart'. No prerequisites or exclusions are mentioned, leaving some ambiguity.

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