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

bedrock-map-builder-mcp

by xRookieFight

fill_region

Fills a defined box with blocks, weighted block mixes, or palette roles using solid, hollow, wall, outline, floor, or ceiling modes, with replace filters and protection for existing blocks.

Instructions

Fill a box with a block, a weighted mix ({"stone":3,"andesite":1}) or a palette role (@wall). mode: solid, hollow, walls, outline, floor, ceiling. only_replace limits the fill to those block types, keep protects them.

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>",
      "block": "<block>"
    },
    "name": "fill_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
keepNo
modeNosolid
undoNo
blockYes
styleNo
dimensionNooverworld
thicknessNo
only_replaceNo

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; it does disclose the block-spec forms and the mode set, which is real behavioral context. However, it never says the operation overwrites existing blocks by default, that an undo parameter exists and defaults to true, or anything about size/permission limits — notable gaps for a destructive bulk-write 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 tight sentences, front-loaded with the core action and then the block-argument forms, followed by mode and the two filters. Slight waste in re-listing the six mode values that the enum already declares, and the inline JSON example reads a bit cluttered without formatting.

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 10-parameter mutation tool with zero annotation coverage and no output schema, the description covers the high-value semantics (block forms, fill shape, replacement filters) but leaves a third of the parameters and the undo/overwrite behavior undocumented. Adequate to call it, not sufficient to call it safely in edge cases.

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 10 parameters, so the description must compensate. It adds genuinely useful meaning for block (weighted-map and palette-role syntax that the schema's bare anyOf does not convey) and brief clauses for only_replace and keep; but from, to, undo, style, dimension, and thickness are untouched, and the mode enumeration merely repeats the schema enum.

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 ("Fill a box") and immediately clarifies the three accepted forms of the block argument, including a concrete weighted-mix example and the @role syntax. It does not differentiate itself from the sibling fill_container, so an agent cannot tell from the text alone which of the two filling tools to pick.

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 only implied — an agent infers you call this when you want to fill a rectangular volume. There is no statement of when to prefer this over fill_container, replace_blocks, or place_blocks, and no exclusions or prerequisites (permissions, region size limits) are given.

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