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

bedrock-map-builder-mcp

by xRookieFight

check_map

Read-only

Run playability checks on a region: detect floating block groups, verify safe spawn points and headroom, test reachability on foot from a start, score symmetry, and find dark spots where hostile mobs could spawn.

Instructions

Playability checks on a region: floating block groups, whether spawn points are safe (floor, headroom, no hazards), whether points can be reached on foot from a start (walk, step up, drop, sprint jumps), symmetry score for competitive maps, and dark spots where hostile mobs could spawn. Uses project markers as spawns when none are given.

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": "check_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
spawnsNo
reach_toNo
symmetryNonone
dimensionNooverworld
dark_spotsNo
reach_fromNo
symmetry_exactNocompare block types too, not just shape (mixed palettes won't pass)
light_thresholdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. Beyond that, the description discloses one genuinely non-obvious behavior: project markers are substituted as spawns when none are supplied. It says nothing about how results are returned, whether the scan is expensive on large volumes, or whether partial results are possible.

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?

A single front-loaded clause establishes the tool's purpose, followed by a compact enumerated list of checks with zero filler. The trailing sentence about project markers is positioned well, though the list-heavy sentence is dense enough that splitting it would aid scanning.

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 analytical tool with no output schema, the definition names the check categories but never describes the return shape (scores? coordinate lists? per-check verdicts?), which is the main thing an agent needs to consume the result. Two parameters (dimension, light_threshold) and their effect on the checks are left undocumented.

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 only 10% across 10 parameters, so the description must carry the load; it partially does by mapping spawns/reach_from/reach_to, symmetry, and dark_spots to the described checks. However, 'dimension' (nether/end vs overworld) and 'light_threshold' are never mentioned, and 'from'/'to' bounds are only implied by the word 'region'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Playability checks on a region') and then enumerates the five concrete checks performed: floating block groups, spawn safety, foot reachability, symmetry score, and dark spots. None of the siblings (region_stats, find_blocks, region_mark) covers playability analysis, so the purpose is unmistakable.

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 implied by the enumeration of checks — an agent can infer this is the tool for validating a built map before publishing. But there is no explicit when-to-use/when-not guidance, no mention of cost or volume limits for large regions, and no pointer to an alternative for simpler statistics.

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