Skip to main content
Glama

Create the planned test server

create_server

Creates a private Minecraft test server from an approved plan by downloading and hash-checking official files, optionally installing NeoForge, and writing RCON settings; it does not start the server.

Instructions

Carries out a plan from plan_setup: makes the folder, downloads the server from the official source, checks every hash (nothing is kept if a hash is wrong), runs the NeoForge installer if chosen, and writes server.properties with RCON on 127.0.0.1 and a random password. Does not accept the EULA and does not start the server. Only call this after the person said yes to the plan.

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": {
      "plan_id": "<plan_id>",
      "person_confirmed": "<person_confirmed>"
    },
    "name": "create_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYesplan_id from plan_setup
person_confirmedYestrue only after you showed the person the plan (downloads, sources, folder, ports) and they said yes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say it is non-read-only, open-world, non-idempotent, and non-destructive; the description adds the substance: it downloads from an official source, verifies every hash and keeps nothing on mismatch, writes server.properties with RCON bound to 127.0.0.1 using a random password, and deliberately stops short of EULA acceptance and server start. Those are meaningful side-effect and failure-mode disclosures an agent cannot derive from 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?

The operation verb leads, the action sequence follows in order, and the two negative constraints and the confirmation gate close it out. It is a dense single sentence plus caveats with no filler or redundancy.

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 two-parameter, non-idempotent setup tool with no output schema, the description covers inputs, side effects, and failure behavior well. The one gap is that it never indicates what the call reports back on success (e.g. resulting server identity or file paths), leaving the agent to discover the response shape at runtime.

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 both parameters are already documented, including the const:true on person_confirmed. The description still reinforces the semantics by tying the call to a plan_setup plan and repeating the confirmation gate, but it does not explain what plan_id refers to beyond the schema's own wording.

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 ("Carries out a plan from plan_setup") and then enumerates the concrete actions: creating the folder, downloading from the official source, verifying every hash, running the NeoForge installer, and writing server.properties. This is clearly distinguishable from every sibling (plan_setup, start_server, accept_eula) because it names its upstream input and its own boundary.

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?

Gives an explicit gating condition ("Only call this after the person said yes to the plan") and explicitly scopes out two adjacent operations ("Does not accept the EULA and does not start the server"), which routes the agent to accept_eula and start_server for those steps. When-to-use, when-not, and the confirmation prerequisite are all present.

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