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

bedrock-map-builder-mcp

by xRookieFight

server_start

Starts the Bedrock Dedicated Server on a specified managed world, stopping any other running world. Automatically attaches the bridge pack so you can build, edit, and verify Minecraft Bedrock maps.

Instructions

Start the server on a managed world (stops whatever else was running). The world gets the bridge pack attached automatically.

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": {
      "world": "<world>"
    },
    "name": "server_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
worldYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose the key side effect: starting this server stops whatever else was running, and the bridge pack is attached automatically. It stops short of saying whether the call blocks until ready, what happens with a nonexistent world, or what is returned, but the destructive consequence is front and center.

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?

Two short sentences, zero filler, and the side-effect warning is placed immediately after the action rather than buried. Nothing could be removed without losing information.

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 one-parameter tool with no output schema and no annotations, the definition covers the action, the disruptive side effect, and an automatic post-condition (bridge pack attached). Only the return/lifecycle behavior is unaddressed, which is a minor gap at this complexity level.

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 description coverage is 0% for the single `world` parameter, so the description must compensate. It adds meaningful constraint by calling it a "managed world" (implying a pre-existing registered world rather than an arbitrary path), but gives no naming format or examples.

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?

"Start the server on a managed world" gives a specific verb plus resource, and the parenthetical clarifies the scope of the action. It is clearly distinguishable from server_stop and server_status by the verb alone, though it never names those siblings explicitly.

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: you use this when you want to bring a managed world online. There is no explicit when-not guidance or reference to server_setup for creating a world, so the agent must infer the boundary from the sibling name alone.

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