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

bedrock-map-builder-mcp

by xRookieFight

block_search

Read-only

Search Minecraft Bedrock block IDs by substring, such as 'stairs', 'copper', or 'glass', to identify blocks for map building and edits.

Instructions

Find Bedrock block ids by substring, e.g. 'stairs', 'copper', 'glass'.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe lookup, and the description usefully adds that matching is substring-based rather than exact. It does not disclose matching behavior beyond that (case sensitivity, prefix vs. anywhere, result ordering) or what happens when the default limit of 60 is hit, which is the main behavioral unknown for a search tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the verb and resource, then supplies examples in the fewest possible words. Nothing is redundant or padded.

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 simple two-parameter read tool with safety annotations and no output schema, the description covers the core purpose but leaves the shape of results (bare id list vs. objects) and the effect of limit unexplained. An agent can call it, but cannot predict what comes back or whether to raise the limit.

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%, so the description must carry the parameter burden. The examples ('stairs', 'copper', 'glass') plus 'by substring' adequately pin down what query means, but the limit parameter (default 60, max 300) is never mentioned, leaving truncation behavior 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?

"Find Bedrock block ids by substring" states a specific verb (find), a specific resource (Bedrock block ids) and the matching method (substring), with concrete example queries. This clearly separates it from block_info (look up one known block) or find_blocks (locate placed blocks in the world), though it never names those siblings explicitly.

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 usage context is implied: use it when you only know part of a block name and need the canonical id. There is no explicit statement of when NOT to use it, no pointer to block_info for full details on a found id, and no disambiguation from the similarly named find_blocks, so an agent must infer the routing.

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