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

bedrock-map-builder-mcp

by xRookieFight

world_create

Create a new Minecraft Bedrock world and start its server, using flat or normal terrain with mob spawning, daylight, and weather cycles disabled for building.

Instructions

Create a new managed world and start the server on it. flat is a superflat build plot, default is normal terrain. Mob spawning, daylight and weather cycles are turned off for building.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
seedNo
typeNoflat

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose meaningful behavior: the server is started on the new world, and mob spawning plus daylight/weather cycles are disabled. It does not say what happens when a world with the same name exists, where the world is stored, or what the response looks like, which are notable gaps for a creation tool.

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?

Three short sentences, front-loaded with the action and side effect, then terrain semantics, then environment behavior. Nothing is wasted, though the middle sentence is slightly less clearly framed than it could be.

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 simple 3-parameter creation tool with 1 required parameter and no output schema, the description covers the action, its side effect, and the terrain choice. What remains missing is mostly edge-case behavior (duplicate names, seed semantics, returned identifier), which keeps it just below 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 description coverage is 0%, so the description must compensate. It does explain the `type` enum values (flat = superflat build plot, default = normal terrain), which is genuinely useful beyond the schema, but `name` and `seed` receive no explanation at all (seed format, name uniqueness, max length already in schema).

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 uses a specific verb+resource ("Create a new managed world and start the server on it"), and adds the side effect of starting a server, which distinguishes it from pure listing/import tools. It does not explicitly name a sibling it competes with (e.g., world_import, world_restore), so it stops short of full differentiation.

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?

The phrase "for building" and the flat/default explanation imply the scenario this tool is meant for, giving a reasonable picture of when to reach for it. However, there is no explicit guidance on when to use this versus world_import or world_restore, and no stated prerequisites (e.g., whether a project must be open).

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