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

bedrock-map-builder-mcp

by xRookieFight

run_commands

Run Bedrock commands in a Minecraft world to modify blocks, entities, gamerules, and more, with success or error feedback for each command.

Instructions

Run Bedrock commands in the world (setblock, fill, summon, tp, gamerule, scoreboard, tag, effect, time, weather, structure...). Each command reports success or the game's error text. Bedrock syntax, not Java: e.g. block states use ["state"=value] and there's no NBT. Commands that touch blocks far from players need load_area covering them, otherwise they quietly affect nothing (count 0).

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

Input Schema

NameRequiredDescriptionDefault
commandsYes
dimensionNooverworld
load_areaNo

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, the description carries the full burden and does well: it discloses per-command success/error reporting, the Bedrock-vs-Java dialect difference (block states, no NBT), and the critical silent-no-op behavior when load_area doesn't cover far blocks. It omits permission/op-level requirements and doesn't warn that these commands mutate world state destructively.

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?

Four dense sentences, front-loaded with the capability, then syntax dialect, then the load_area gotcha. No filler or repetition; every sentence adds information an agent needs.

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 3-parameter, nested-schema, no-output-schema mutation tool, the description covers the highest-risk unknowns (silent no-ops, error reporting, syntax dialect). It leaves the dimension parameter and array size limits undocumented, which are the remaining gaps.

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 explains the semantics of commands (each returns success or error text) and of load_area (must cover far-away blocks or the command no-ops with count 0), which is valuable, but the dimension parameter is never mentioned and no limits (500 commands, 32k chars) are conveyed.

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 states a specific verb and resource ("Run Bedrock commands in the world") and lists concrete command families (setblock, fill, summon, tp, gamerule, scoreboard...) so an agent knows exactly what capability this is. It doesn't explicitly name which siblings to prefer for structured edits (e.g. fill_region, place_blocks), so it stops short of full sibling 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?

There is a real usage condition given: commands touching blocks far from players require load_area or they silently affect nothing. However, it never says when to choose this raw-command tool over the higher-level region/block tools in the sibling list, and there are no explicit exclusions.

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