Skip to main content
Glama

Stop the test server

stop_server
Idempotent

Stops the Minecraft test server cleanly via RCON and waits for exit, saving the world. Use force to end an unresponsive process, accepting possible loss of unsaved changes.

Instructions

Stops the test server cleanly through RCON (the world is saved) and waits for it to exit. force: true ends the process if it does not answer; unsaved changes may then be lost.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoEnd the process if it does not answer on RCON. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true; the description adds genuinely new context: the graceful path saves the world, the call blocks until exit, and the force path can lose unsaved changes. That conditional data-loss caveat is the key behavioral nuance an agent needs beyond the annotations.

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 sentences, both load-bearing: the first covers normal operation and its blocking nature, the second covers the fallback and its risk. Nothing is repeated and the risk is placed where it matters.

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

Completeness5/5

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

For a one-optional-parameter shutdown tool with annotations present and no output schema, the description covers mechanism, saved-state guarantee, blocking behavior, and the failure-mode risk. An agent has everything needed to call it correctly and warn about data loss.

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?

Schema coverage is 100% and the schema already explains that force ends an unresponsive process with default false. The description still adds meaning by stating the consequence of forcing, namely that unsaved changes may be lost, which the schema does not say.

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 pairs a specific verb with a specific resource ('Stops the test server') and adds the mechanism ('through RCON (the world is saved)') plus blocking behavior ('waits for it to exit'). It is immediately distinguishable from restart_server or status, though it does not explicitly name a sibling as the alternative.

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?

Usage is implied clearly enough: call this to shut the server down, and reserve force: true for when RCON does not answer. There is no explicit statement of when to prefer restart_server, nor any prerequisite/ordering guidance relative to siblings such as backup_world.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.