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

bedrock-map-builder-mcp

by xRookieFight

find_blocks

Read-only

Locate specific blocks such as chests or diamond ore within a Minecraft Bedrock region and return their coordinates, capped by a limit.

Instructions

Find where certain blocks are inside a region (e.g. all chests, all diamond_ore, stray barrier blocks). Returns positions, capped by limit.

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

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
limitNo
blocksYes
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe, non-mutating operation, so the description's main added value is disclosing that results are positions and that the count is capped by limit. It does not disclose cost/performance on large volumes, whether truncation is signalled to the caller, or ordering of results – useful context for a search over a potentially huge region.

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 with the core action front-loaded and the return behavior second; nothing is redundant. It is arguably slightly too terse given the parameter surface it needs to cover, but there is no wasted wording.

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 tool with five parameters, nested coordinate objects, an enum dimension, and no schema descriptions or output schema, the description is under-specified. It never explains how the region is bounded (from/to), what coordinate convention or dimension default applies, or what a returned position looks like.

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% across 5 parameters, including nested from/to coordinate objects, so the description carries the full burden. It only touches blocks (via examples) and limit (via 'capped by limit'); the region bounds and the dimension enum are never mentioned, leaving the caller to reverse-engineer required parameters from the schema alone.

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?

The description gives a specific verb and resource ('Find where certain blocks are inside a region') plus concrete examples (chests, diamond_ore, barrier blocks), so an agent immediately knows this is a spatial block-search. It does not differentiate from the sibling block_search or region_stats, which is the only thing keeping it from a 5.

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 examples imply the intended use case (locating structures or specific materials in an area), which is enough to infer when to call it. However, there is no explicit when-to-use vs. when-to-use-something-else guidance, and the existence of a sibling named block_search makes the missing differentiation a real gap.

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