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

bedrock-map-builder-mcp

by xRookieFight

region_mark

Names a Minecraft region by coordinates so later requests can reference it; pass only the name to delete that saved region.

Instructions

Name a region (spawn area, arena, district...) so later requests can refer to it by name. Pass only name to delete.

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

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
nameYes
noteNo
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the whole burden. It discloses the destructive name-only delete mode, which is genuinely valuable, but says nothing about overwrite semantics for existing names, whether from/to must both be supplied, whether partial corners are rejected, how note is stored, or which dimension a region defaults to in practice.

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 compact sentences, front-loaded with the primary create/name behavior and following with the delete shortcut. No filler, though the parenthetical examples cost a few words for real clarifying value.

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?

A mutation tool with nested coordinate objects, an enum dimension parameter, zero annotation coverage, and no output schema needs considerably more explanation. Missing are coordinate semantics, default dimension behavior, overwrite/duplicate handling, and what a successful mark returns.

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% for five parameters, so the description must compensate. It explains name and the name-only delete form, but from/to corners, note, and the dimension enum (overworld/nether/the_end) are entirely undocumented in both schema and text, leaving the most error-prone parameters unexplained.

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 (name) plus resource (a region) and gives concrete examples (spawn area, arena, district) that clarify the concept. It also implies a second mode (deletion) via the sentence about passing only name. It does not distinguish itself from siblings like clear_region, but the action itself is unambiguous.

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?

The description supplies one conditional rule: pass only name to delete. It gives no guidance on when to use this versus clear_region, markers, or copy_region, nor does it state whether a name already in use is overwritten or rejected. Usage is thereby implied rather than spelled out.

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