Skip to main content
Glama

Plan a test server (changes nothing)

plan_setup
Read-onlyIdempotent

Previews a local Minecraft test server setup without changing anything: resolves the game version, required Java, files with official hashes, folder and ports for review before creation.

Instructions

Looks up everything needed for a new local test server and changes nothing: the exact Minecraft (and NeoForge) version, which Java it needs and whether it is installed, every file that would be downloaded with its official source and hash, the folder and the ports. Show the result to the person and ask before create_server. Minecraft Java Edition 1.20.1 or newer.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "minecraft": "<minecraft>",
      "loader": "<loader>"
    },
    "name": "plan_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFolder name for the server. Default "test-server".test-server
loaderYesvanilla, or neoforge for modpacks
game_portNoPort to join on. Default: the first free port from 25565.
java_pathNoA specific java executable to use
memory_mbNoMemory for the server. Default 2048 (vanilla) or 4096 (NeoForge).
minecraftYesMinecraft version such as "1.21.11", or "latest" for the newest release
rcon_portNoRCON port on 127.0.0.1. Default: the first free port from 25575.
world_typeNoflat (default, good for building) or normal terrain
server_folderNoWhich allowed folder to put it in (see status). Default the first one.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so safety is covered; the description adds that the plan includes Java install status, per-file official source and hash, folder and ports — information the agent cannot get from annotations. It stops short of describing failure behavior, e.g. what is returned when Java is missing or the version is too old.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the read-only planning purpose and the what-you-get list, then the workflow instruction. The trailing version-requirement fragment is a slightly awkward placement but carries real constraint value, so little is wasted.

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?

For a 9-parameter, no-output-schema tool this does the heavy lifting: it describes the shape of the returned plan and the human-approval step. What is missing is error/edge behavior — unsupported versions, no allowed folder, or Java not installed — which the agent would need to handle gracefully.

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%, so the baseline is 3; the description earns above that by adding a constraint the schema lacks — the 1.20.1+ version floor applying to the 'minecraft' parameter, which the schema allows as any string or 'latest'. Folder and port mentions tie back to parameters but add little beyond the schema.

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 a specific verb and resource ('looks up everything needed for a new local test server') and immediately scopes it with 'changes nothing', which separates it from create_server. The enumeration of what gets resolved (version, Java, files, folder, ports) makes the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit sequencing: 'Show the result to the person and ask before create_server' names the alternative and the precondition that selects it. It also states the supported floor, 'Minecraft Java Edition 1.20.1 or newer', so the agent knows when not to trust a plan.

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