Skip to main content
Glama

Switch to another test server folder

use_server
Idempotent

Activates an allowed Minecraft server folder so agents can use it, adopting existing servers by detecting startup and preserving settings while binding RCON to 127.0.0.1.

Instructions

Makes another server folder the active one. It must be inside one of the allowed server folders in the person's config (see status). A server this tool did not make is adopted: the tool works out how to start it and keeps its settings, except that it always keeps RCON on 127.0.0.1.

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": {
      "folder": "<folder>"
    },
    "name": "use_server"
  }
}

Input Schema

NameRequiredDescriptionDefault
folderYesFull path of the server folder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare idempotent, non-destructive, non-open-world, and not read-only; the description goes beyond them by disclosing the adoption path, that existing settings are preserved, and that RCON is forcibly pinned to 127.0.0.1 — a real side effect an agent should know about. It does not say what happens on failure or whether the switch can be undone/reverted, which keeps it below a 5.

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 action, followed by the constraint, then the adoption caveat; three sentences and each carries information. The final clause about RCON is slightly cramped in phrasing but is substantive rather than filler.

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?

No output schema exists, so the description ideally would hint at the return value, and it does not. Otherwise it is complete for a one-parameter state-switching tool: precondition, adoption semantics, settings preservation, and the RCON override are all covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single 'folder' parameter is already documented as a full path, so the schema carries most of the semantic load and the baseline is 3. The description adds one genuine constraint — the path must reside within an allowed server folder listed in the person's config — but gives no examples or path-format guidance beyond that.

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?

States a specific verb and effect: 'Makes another server folder the active one.' That is unambiguous and lets an agent distinguish it from create_server (which makes a new server) because the description explains that an existing, foreign server is adopted rather than created. It stops short of naming a sibling explicitly, so it is a clear but not fully differentiating 4.

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?

Gives one hard precondition — the folder must lie inside an allowed server folder in the person's config, with a pointer to status to discover those folders. Usage is otherwise implied by the verb; there is no explicit 'use this instead of X' guidance or statement of when not to call it (e.g. versus create_server for a brand-new folder).

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