Skip to main content
Glama

Edit blocks from a 3D array

edit_blocks
DestructiveIdempotent

Bulk-place or modify many different Minecraft blocks in one call via a 3D array, supporting block states and NBT; arrays over 100,000 blocks are rejected.

Instructions

Place many different blocks in one call from a 3D array (MCPyLib's bulk edit). build_from_layers is usually easier to write. Refuses arrays whose bounding box exceeds 100,000 blocks.

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": {
      "x": "<x>",
      "y": "<y>",
      "z": "<z>",
      "blocks": "<blocks>"
    },
    "name": "edit_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYesX of the array's lowest corner.
yYesY of the array's lowest corner.
zYesZ of the array's lowest corner.
blocksYesRectangular array indexed blocks[x][y][z] relative to the corner. Each entry is a block id, an object {block, block_state?, nbt?}, or null to leave that position unchanged.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive=true, idempotent=true and openWorldHint=false, so the safety profile is covered. The description adds a real constraint not in the structured fields: arrays whose bounding box exceeds 100,000 blocks are refused. It leaves out permission requirements and whether a partially out-of-range call is atomic, but the size limit is meaningful added context.

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?

Three short sentences, front-loaded with what the tool does, then the easier alternative, then the hard limit. No filler and nothing buried.

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

Completeness4/5

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

With full schema coverage, an output schema, and annotations covering safety and idempotency, the agent has nearly everything needed to call this correctly; the 100,000-block refusal rule closes the main gap. Remaining omissions (permissions, partial-failure behavior) are minor for a well-annotated bulk-write tool.

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 100%, and the schema already explains the corner coordinates, the blocks[x][y][z] indexing, the null-means-unchanged convention, and the block_state handling in detail. The description restates the 3D-array shape but adds no format or semantic detail beyond what the schema provides, so baseline 3 applies.

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?

Specific verb plus resource plus mechanism: 'Place many different blocks in one call from a 3D array'. It also flags itself as the bulk/'MCPyLib' variant, which separates it from single-block tools like get_block and from the sibling build_from_layers without needing the schemas opened.

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

Usage Guidelines4/5

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

It explicitly points to build_from_layers as the usually-easier alternative, so an agent knows a preferred sibling exists. What is missing is the inverse condition — when the 3D-array form is actually the right choice (e.g. when the caller already holds a nested array) — so selection is implied rather than fully stated.

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