Skip to main content
Glama

stop_server

Gracefully stop the Minecraft server using RCON commands, with fallback methods to ensure shutdown completion.

Instructions

Gracefully stop the Minecraft server. Uses RCON 'stop' command, falls back to stdin, then SIGKILL after 30s.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Registration and handler definition for the "stop_server" tool. It calls manager.stop().
    server.tool(
      "stop_server",
      "Gracefully stop the Minecraft server. Uses RCON 'stop' command, falls back to stdin, then SIGKILL after 30s.",
      {},
      async () => {
        const result = await manager.stop();
        return { content: [{ type: "text", text: result }] };
      }
    );
Behavior5/5

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

Excellent disclosure of implementation details and failure modes: specifies RCON 'stop' as primary method, stdin fallback, and SIGKILL escalation after 30s timeout. Since no annotations exist, this description carries the full burden of explaining the destructive escalation chain.

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?

Single sentence, front-loaded with purpose ('Gracefully stop'), followed by mechanism. No redundant words; dense information (89 characters) covering intent, implementation, and timeout behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a zero-parameter action tool. Describes the operation mechanism sufficiently for invocation. No output schema exists; description hints at async nature via timeout but doesn't detail return values, which is acceptable given the simple action paradigm.

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?

Baseline score for zero parameters per rubric. Schema is empty object with 100% coverage trivially. No parameter documentation needed or provided.

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?

States specific action ('Gracefully stop') and target resource ('Minecraft server'). Implicitly distinguishes from sibling 'restart_server' (which implies stop+start cycle) and 'start_server' by focusing solely on termination.

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?

Provides implicit usage through the specific verb 'stop', but lacks explicit guidance on when to choose this over 'restart_server' or prerequisites (e.g., warning players). No 'when-not' or alternative recommendations stated.

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