Skip to main content
Glama
bedrock-map-builder-mcp

bedrock-map-builder-mcp

by xRookieFight

server_setup

Points the map builder at an unpacked Linux Bedrock Dedicated Server folder containing bedrock_server, auto-detects the newest when enabled, and sets the player join port.

Instructions

Point the builder at an unpacked Linux Bedrock Dedicated Server (the folder with bedrock_server). With detect=true it searches Downloads and similar folders and picks the newest. Also sets the game port players can join on.

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

Input Schema

NameRequiredDescriptionDefault
detectNo
bds_dirNo
server_portNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses that detect=true searches local folders and picks the newest, and that the tool sets the join port, but it does not explain what configuration is modified, whether existing settings are overwritten, what permissions are required, or what happens on failure.

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 description is three focused sentences with no wasted wording. Purpose is front-loaded, followed by detect behavior and port setting, making it easy to scan.

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

Completeness3/5

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

For a setup tool with no annotations, no output schema, and 0% schema description coverage, the description covers the core purpose and all three parameters at a basic level. It remains incomplete around side effects, defaults, prerequisites, and result behavior, so it is adequate but not fully complete.

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 0%, so the description must compensate. It gives useful meaning for all three parameters: detect triggers folder search and newest selection, bds_dir is the folder containing bedrock_server, and server_port is the join port. It still omits defaults and whether bds_dir is ignored when detect=true.

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 states a specific verb and resource: point the builder at an unpacked Linux Bedrock Dedicated Server folder containing bedrock_server, and set the game port. It is clearly a setup/configuration tool rather than a server control sibling like server_start or server_stop, though it does not explicitly name those alternatives.

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 as initial server setup, and detect=true is described as searching Downloads and similar folders to pick the newest server. However, there is no explicit when-to-use guidance versus alternatives, no prerequisites, and no statement of when detect should be false or bds_dir should be used directly.

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