Skip to main content
Glama

Read blocks in a box

get_blocks
Read-onlyIdempotent

Reads all blocks in a Minecraft box and returns palette layers, XYZ indices, or counts for inspecting terrain and preparing edits.

Instructions

Read every block in a box (corners inclusive, any order; at most 100,000 blocks).

The default 'layers' layout returns palette (character -> block id) and layers: one entry per Y from the bottom up, each a list of row strings from north to south (+Z), each row read west to east (+X). '.' is air. It is the exact input format of build_from_layers, so you can edit the strings and write them back. counts gives the number of each block. Keep raw reads small (16x16x16 is plenty); use layout='summary' or get_height_map for big areas.

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": {
      "x1": "<x1>",
      "y1": "<y1>",
      "z1": "<z1>",
      "x2": "<x2>",
      "y2": "<y2>",
      "z2": "<z2>"
    },
    "name": "get_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
x1YesX of one corner of the box (inclusive).
x2YesX of the opposite corner (inclusive).
y1YesY of one corner of the box (inclusive).
y2YesY of the opposite corner (inclusive).
z1YesZ of one corner of the box (inclusive).
z2YesZ of the opposite corner (inclusive).
layoutNo'layers' (default): character palette + layers[y][z] strings, the format build_from_layers accepts. 'xyz': palette indices as blocks[x][y][z], the edit_blocks format. 'summary': block counts only.layers

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavior: the hard 100,000-block cap, the '.' = air convention, and the exact axis/ordering conventions of the returned layers (Y bottom-up, rows north-to-south, west-to-east). It stops short of saying what happens on oversized or unloaded-chunk requests, which is the one behavioral gap.

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?

Three short, front-loaded paragraphs: purpose and cap first, output format second, sizing guidance last. No filler sentences, though the layout explanation partially duplicates the enum description in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter read tool with a full output schema and complete annotations, the description supplies everything an agent needs to call it correctly and to consume the result: size limits, coordinate/ordering conventions, and interop with build_from_layers and edit_blocks.

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 coverage is 100% and the layout enum description in the schema already spells out 'layers', 'xyz' and 'summary' including the build_from_layers/edit_blocks format mapping. The description largely restates that same layout text, adding only the '.' = air note. Baseline 3 is appropriate when the schema does the heavy lifting.

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 ('Read every block in a box') plus concrete scope semantics: corners inclusive, any order, at most 100,000 blocks. It is immediately distinguishable from get_height_map and get_block, which are named or implied by the summary guidance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives explicit when-not guidance ('Keep raw reads small (16x16x16 is plenty); use layout='summary' or get_height_map for big areas') and names a downstream alternative workflow (build_from_layers). Both the size condition and the specific substitute tools are stated rather than left to inference.

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