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

bedrock-map-builder-mcp

by xRookieFight

place_blocks

Set up to 20,000 individual Minecraft Bedrock blocks at exact coordinates, with block names validated and states specified as [state=value].

Instructions

Set individual blocks at exact coordinates (up to 20000). Block names are checked first; states use the [state=value] form.

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": {
      "blocks": "<blocks>"
    },
    "name": "place_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
undoNo
blocksYes
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 two useful traits: a hard 20000-block cap and that block names are validated before states are applied. It says nothing about the undo behavior (which defaults to true in the schema), dimension targeting, or what happens on partial failure — significant gaps for a world-mutating tool.

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?

Two dense sentences with the coordinate scope and size cap front-loaded, and no wasted words. 'Block names are checked first' is slightly elliptical about what they are checked against, but the information density is high overall.

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 mutation tool with no annotations, no output schema, and zero schema description coverage, the definition covers the essentials of coordinates, size limit, and block syntax. It leaves undo semantics and dimension selection unexplained, which an agent needs before safely issuing a write.

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 and it only partly does: it explains the 'block' string format including the [state=value] state syntax and confirms the 20000 item limit. The x/y/z coordinate semantics, the undo flag, and the dimension default are left entirely to the bare schema.

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?

States a specific verb and resource ('Set individual blocks') plus the operating scope ('at exact coordinates'), which separates it from region-fill style siblings. It does not name any sibling explicitly, so the 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance; the agent must infer that this is for discrete block placement rather than bulk operations like fill_region or replace_blocks. The '(up to 20000)' cap hints at the batch scale but is not framed as a selection criterion against alternatives.

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