Skip to main content
Glama

Start the test server

start_server
Idempotent

Launches the active Minecraft test server in the background, restores required localhost/RCON settings, and waits until RCON is ready so you can join at localhost:.

Instructions

Starts the active test server in the background and waits until RCON answers (the first start makes the world and can take a minute or two). Before starting it puts back the settings the tool depends on: listen on 127.0.0.1 only, RCON on, no query port. The person then joins in Minecraft at localhost:.

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": "start_server"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world, so the bar is lower, yet the description adds real behavior: it blocks until RCON answers, first start generates the world and may take a minute or two, and it rewrites config (127.0.0.1 only, RCON on, no query port) before starting. That config mutation is exactly the kind of side effect annotations cannot express. It stops short of saying what happens if the server is already up or what a failure looks like.

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?

Three sentences, front-loaded with the action, then latency expectation, then side effects, then the human follow-up. Every sentence carries information an agent or user needs; nothing is repeated from the title or annotations.

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?

With no output schema and no parameters, the description carries the burden and mostly meets it: it explains blocking behavior, duration, config side effects, and the human join step. The only soft spot is the unresolved '<game port>' placeholder, which leaves the agent without a concrete way to report the connection address.

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?

The tool takes zero parameters, so there is no parameter semantics to document and the baseline applies. The description's mention of the game port correctly signals that the port is not an input but an environment value the agent must read elsewhere.

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 opens with a specific verb and resource ('Starts the active test server in the background') and clarifies scope with 'active', which implies a prior selection step. It is clearly distinguishable from stop/restart siblings, though it never names them explicitly to sharpen the boundary.

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 rather than stated: 'the active test server' tells the agent a server must already be selected, and the closing sentence points to the next human step (joining at localhost). There is no explicit guidance on when to prefer this over create_server or restart_server, and no exclusion for an already-running server.

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