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

bedrock-map-builder-mcp

by xRookieFight

region_stats

Read-only

Counts blocks in a world region and returns totals, most-used blocks, and share percentages to check a palette or estimate materials.

Instructions

Count what's in a region of the world: block totals, the most used blocks and their share. Good for checking a palette or estimating materials.

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

Input Schema

NameRequiredDescriptionDefault
toYes
fromYes
dimensionNooverworld

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds value by disclosing the shape of the result (totals plus top blocks and their share), which matters since there is no output schema. It omits any note on cost, scan limits, or how many top blocks are returned.

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?

Two tight sentences with the resource and outputs front-loaded and the use cases second. No filler or redundancy.

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 read-only counting tool with no output schema, the description adequately conveys purpose and return content. However, the nested coordinate bounds and the dimension selector are undocumented, which is a real gap for a spatial query tool.

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 coverage is 0% and the description never mentions the three parameters. The nested from/to coordinate objects and especially the 'dimension' enum (overworld/nether/the_end) go unexplained, leaving the agent to infer region bounds and dimension selection 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?

States a specific verb and resource ('Count what's in a region of the world') and enumerates the outputs (block totals, most used blocks and their share). This distinguishes it from mutation siblings like fill_region or clear_region, though it doesn't explicitly separate it from 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers two concrete use cases ('checking a palette or estimating materials'), which gives implied when-to-use guidance. It never states when not to use it or names an alternative for the related lookup tasks, so an agent still has to infer routing.

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