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

bedrock-map-builder-mcp

by xRookieFight

view

Read-only

Render isometric, top-down, slice, or heightmap images of Minecraft Bedrock builds and world regions, with optional markers, to preview maps before editing or export.

Instructions

Render a picture. source=last shows the last generated or imported build without touching the world; source=world reads a region. mode: iso (isometric 3D, view 0-3 picks the corner), top (top down), slice (vertical cut at slice_at along slice_axis), heightmap (terrain colours for big areas, cheap). Markers from the project can be drawn on top.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
modeNoiso
viewNo
sourceNolast
max_sizeNo
slice_atNo
dimensionNooverworld
slice_axisNoz
show_markersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, and the description usefully reinforces that with "without touching the world" and adds a cost hint for heightmap. It says nothing about what is actually returned (image size/format), how max_size affects output, or any limits, so it adds only modest context beyond the annotation.

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 core action, then grouped by source and by mode, with no filler sentences. The telegraphic style ("cheap", "vertical cut at slice_at along slice_axis") is dense but still readable.

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?

With ten parameters, no schema descriptions, and no output schema, the definition should say more than it does — particularly about the to/from region bounds that source=world depends on, and about dimension. It is adequate to get a basic render call right but leaves an agent guessing on several inputs.

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 carry the load: it explains source, mode, view ("0-3 picks the corner"), slice_at/slice_axis, and that project markers can be overlaid. However, to/from (the region bounds), max_size, and dimension are never mentioned, leaving four of ten parameters entirely undocumented.

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 opening verb+object ("Render a picture") is specific and, combined with the source/mode discussion, makes clear this is the visualization tool rather than a world-mutating one. It does not name a sibling, but the distinction from editing tools is implicit in "without touching the world."

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?

It gives real selection guidance between the two sources ("last ... without touching the world" vs "world reads a region") and recommends heightmap "for big areas, cheap." What is missing is an explicit statement of when not to use this tool or which sibling to use instead for related tasks.

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