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

bedrock-map-builder-mcp

by xRookieFight

map_functions

Write Minecraft Bedrock .mcfunction game logic into a behavior pack in the managed world, with immediate reload and tick function support.

Instructions

Write game logic as .mcfunction files into a behavior pack inside the managed world (Bedrock's replacement for command block chains). Functions are called with /function ; names listed in tick run every tick. The server reloads them right away. Example: {"teams/tp_red": ["tp @a[tag=red] 10 65 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": {
      "functions": "<functions>"
    },
    "name": "map_functions"
  }
}

Input Schema

NameRequiredDescriptionDefault
tickNo
worldNo
functionsYes
replace_allNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/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 disclose useful behavior: files land in a behavior pack in the managed world, the server reloads them immediately, and tick-listed functions execute every tick. However, it does not explain what replace_all does (overwrite vs merge), whether existing files not mentioned are preserved or destroyed, or whether the world must be running for the reload to apply.

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?

It is front-loaded with the core action, then adds execution semantics, then a compact concrete example. Every sentence adds information with no filler; only minor tightening is possible.

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 four-parameter write tool with no annotations and no output schema, the description covers the main functions map well but leaves the overwrite/merge behavior of replace_all and the meaning of world unspecified. An agent could construct a call but might unintentionally overwrite or fail to target the right world.

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% across four parameters, and nested objects are present, so the description must compensate. The inline example clarifies the shape of the complex functions map (name to array of commands) and the tick list semantics, which is valuable. But the world scoping parameter and replace_all's default/replace semantics are never explained, leaving two of four parameters 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 description uses a specific verb and resource: write game logic as .mcfunction files into a behavior pack in the managed world. It also explains the execution model (invoked via /function, tick entries run every tick), which lets an agent recognize this as function-file authoring rather than runtime command execution. It stops short of explicitly contrasting itself with a sibling like run_commands, so sibling differentiation is implied rather than stated.

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 implied by the explanation of how functions are called and how tick-listed names run every tick, which hints at when to use it (persistent logic vs one-off commands). There is no explicit when-to-use/when-not-to-use guidance and no named alternative for executing commands directly.

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