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

bedrock-map-builder-mcp

by xRookieFight

replace_blocks

Swap one or more block types for another block or mix within a defined box, leaving all other blocks unchanged; matching uses block type and ignores states.

Instructions

Swap one or more block types for another block or mix inside a box, leaving everything else alone. Matches by block type, states are ignored when matching.

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>",
      "find": "<find>",
      "replace_with": "<replace_with>"
    },
    "name": "replace_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
findYes
fromYes
undoNo
dimensionNooverworld
replace_withYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose matching semantics ('states are ignored when matching') and non-destructive scope, but says nothing about the undo parameter that defaults to true, the dimension target, or what happens when replace_with is a weighted mix — important for a mutation tool with zero annotation coverage.

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 sentences, front-loaded with the action and followed by the matching rule. No filler, though the second sentence could be tightened and the region-definition detail is absent rather than trimmed.

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 6-parameter mutation tool with nested objects, no annotations, and no output schema, the description covers the core matching behavior but leaves reversibility (undo default true), dimension selection, and the from/to corner semantics unaddressed.

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 6 parameters, so the description must compensate. It does clarify find (one or more block types) and replace_with ('another block or mix', explaining the string-or-object anyOf), and implies from/to form a box, but undo and dimension are entirely undocumented in both schema and description.

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: 'Swap one or more block types for another block or mix inside a box.' The scope is bounded ('leaving everything else alone'), which distinguishes it from a wholesale fill or place operation, though no sibling tool is named explicitly and 'box' is not defined as the from/to cuboid.

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?

'Leaving everything else alone' implies the use case: targeted replacement of matching blocks rather than overwriting a whole region. However, it never states when to prefer this over fill_region or place_blocks, nor any prerequisites such as coordinate ordering or permissions.

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