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

bedrock-map-builder-mcp

by xRookieFight

clear_region

Sets a defined box region to air while preserving specified blocks, such as bedrock, so you can clear space without deleting protected blocks.

Instructions

Set a box to air (keep lets some blocks survive, e.g. bedrock).

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

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
keepNo
undoNo
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/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 burden of behavioral disclosure. It mentions that keep lets some blocks survive, but omits the destructive nature, undo default, dimension scope, permissions, and return behavior.

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?

The definition is a single front-loaded sentence with no wasted filler. It is concise, though the parenthetical wording is slightly informal.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive five-parameter region tool with nested coordinates, default undo, enum dimension, no annotations, and no output schema, the description is too sparse. It does not give enough information to call the tool correctly beyond the basic clearing intent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 for five parameters. It only partially explains keep with a bedrock example and implies from/to via "box," leaving coordinate semantics, dimension, and undo 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?

States a specific action, "Set a box to air," and adds the keep exception, so the tool's purpose is identifiable. It does not distinguish this from sibling region tools such as fill_region or replace_blocks.

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?

Provides no explicit when-to-use or when-not guidance and does not name alternatives. The keep clause implies selective clearing but does not explain when to choose this over fill_region or replace_blocks.

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