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

bedrock-map-builder-mcp

by xRookieFight

block_info

Read-only

Retrieves a Minecraft block's states and allowed values, maps Java IDs to Bedrock names, and suggests corrections for typos.

Instructions

States and allowed values of a block, with the Bedrock name for Java ids and suggestions for typos.

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

Input Schema

NameRequiredDescriptionDefault
blockYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With readOnlyHint=true already covering the safety profile, the description adds real behavioral context: it discloses that invalid input yields typo suggestions and that Java ids get a Bedrock name mapping. It stops short of describing the response shape, whether states include defaults, or whether it errors on unknown blocks.

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?

One compact sentence with no filler, and the primary capability (states and allowed values) is front-loaded ahead of the secondary Bedrock-name and typo-suggestion details.

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 single-parameter lookup tool with no output schema, the description is adequate but thin: it gestures at return content without explaining structure, and leaves input format ambiguity unresolved, which matters for an id-based lookup.

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?

The single 'block' parameter has 0% schema description coverage, so the description must carry the meaning. It partially does — mentioning Java ids implies the expected identifier flavor — but it never states accepted syntax (namespace:name, state/property notation) or whether Bedrock ids are also accepted.

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 names a specific resource (a block) and what is returned about it: states and allowed values, the Bedrock name for Java ids, and typo suggestions. That is substantive and distinguishable from a search tool, though it never explicitly contrasts itself with siblings like block_search or find_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?

There is no when-to-use guidance at all — no statement of when to call this instead of block_search or find_blocks, and no prerequisites. The only implied usage cue is that it helps with typos, which hints at validation use but is not framed as guidance.

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