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

bedrock-map-builder-mcp

by xRookieFight

generate

Build Minecraft Bedrock structures, terrain, and scenes with generators, then place them in-world or preview them with dry_run before committing.

Instructions

Build something with a generator and write it into the world (undoable), or preview it with dry_run (no world needed). Generators: shapes, script, house, tower, wall, castle, bridge, road, skyscraper, city, arena, parkour, lobby, dungeon, tree, vegetation, terrain, sculpt, river, lake, caves, mountain. Call generator_help for arguments. Returns markers (spawns, doors, chests, checkpoints...) for follow up steps like set_spawn or fill_container. preview adds a rendered image.

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

Input Schema

NameRequiredDescriptionDefault
argsNo
undoNo
labelNo
facingNosouth
originNo
dry_runNo
previewNo
dimensionNooverworld
generatorYes
resume_opNoop id of an interrupted run of the exact same call, finished tiles are skipped

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 supplied, the description carries the full burden and does well: it discloses that the write is undoable, that dry_run needs no world, that the call returns markers usable in follow-up steps like set_spawn or fill_container, and that preview adds a rendered image. It omits anything about cost/latency of large generators or what happens to overlapping existing terrain.

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-loads the core write/preview distinction before the long generator enumeration, and the marker/return note is placed after it. The generator list is long but load-bearing rather than filler; sentences are terse and each adds a distinct fact.

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 10-parameter mutating tool with no annotations and no output schema, the description usefully substitutes for the missing output schema by describing returned markers. It is still incomplete on the spatial parameters (origin, dimension, facing) and on undo semantics, which an agent needs to place a build correctly.

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 only 10% across 10 parameters, so the description must compensate; it adds real meaning for generator (full enumeration), dry_run (no world needed) and preview (renders an image) and points to generator_help for args. But origin, dimension, facing, undo, label and resume_op are left entirely to the bare schema, including the non-obvious default undo=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?

Uses a concrete verb+resource ('build something with a generator and write it into the world') and enumerates all supported generators, so the agent knows exactly what this produces. It falls short of a 5 only because it never contrasts itself with build-adjacent siblings such as place_blocks or fill_region.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear operating guidance: write for real (undoable) versus dry_run to preview with no world required, and directs the agent to generator_help for per-generator arguments. It does not state any when-not-to-use condition or alternative for non-generator building, so it stops short of explicit alternatives.

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