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

bedrock-map-builder-mcp

by xRookieFight

copy_region

Copies, moves, rotates, mirrors, or repeats a defined block region to a destination coordinate in Minecraft Bedrock maps, with options to skip air and undo changes.

Instructions

Copy, move, rotate, mirror or repeat a region. dest is where the source's min corner ends up. rotate is quarter turns clockwise (block facing rotates too). repeat > 1 stacks copies every step. move clears the source. skip_air leaves the destination's existing blocks where the source has air. Chest contents and other block entity data are not copied.

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": {
      "from": "<from>",
      "to": "<to>",
      "dest": "<dest>"
    },
    "name": "copy_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
destYes
fromYes
moveNo
stepNo
undoNo
mirrorNonone
repeatNo
rotateNo
skip_airNo
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 whole burden and does substantial work: it discloses that move is destructive to the source, that block entity data such as chest contents is not copied, and that block facing rotates with rotate. It omits the undo parameter's behavior, which matters greatly for a destructive operation whose undo defaults to true.

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?

Seven short sentences, the primary operation front-loaded and each option explained in one clause. Nothing is padded and the ordering follows the order an agent would reason about the call.

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 an 11-parameter, nested-object, high-impact tool with no annotations and no output schema, the description is informative but incomplete: return behavior is unmentioned and the undo parameter, the only safety valve on a destructive move, is never explained.

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 and it partially does: dest, step, rotate, repeat, move and skip_air all get real meaning beyond their bare names. Five of eleven parameters are left unaddressed, notably the mirror axis values (none/x/z), dimension, and undo, so the gap is only half closed.

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 first sentence names a concrete verb set (copy, move, rotate, mirror, repeat) acting on a clearly bounded resource (a region defined by from/to). It is distinguishable from clear_region and fill_region on substance, though it never names a sibling for contrast.

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 conveyed indirectly through option semantics: move clears the source, repeat>1 stacks copies, skip_air preserves the destination. There is no explicit 'use this instead of X when Y' routing, and no prerequisites or permission notes are given.

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