Skip to main content
Glama

Place blocks

place_blocks
DestructiveIdempotent

Places up to 10000 Minecraft blocks in one call, batching equal neighbors into fill commands, ordering torches, doors, and liquids correctly, and snapshotting the area so undo can restore it.

Instructions

Places single blocks, up to 10000 per call. The tool packs neighbouring equal blocks into /fill commands, places torches, doors, plants, redstone and liquids after the blocks that hold them, and snapshots the area first so undo can put it back. Later entries at the same spot win.

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": {
      "blocks": "<blocks>"
    },
    "name": "place_blocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
blocksYesBlocks to place: [{pos: [x, y, z], block: "minecraft:stone"}, ...]
dimensionNoDimension. Default overworld.overworld
skip_backupNoOnly for areas too big for an undo snapshot, after backup_world. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.9/5.0
Behavior5/5

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

Beyond the annotations (destructive=true, idempotent=true) it discloses genuinely non-obvious behavior: batching into /fill commands, placement ordering so torches/doors/plants/redstone/liquids go after their supporting blocks, an automatic area snapshot enabling undo, and last-write-wins for duplicate positions. The last-write rule also corroborates the idempotentHint rather than conflicting with it.

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?

Two dense sentences with the primary action and capacity front-loaded, followed by placement semantics. The middle sentence is a long list that is slightly hard to parse, but every clause carries real information and nothing is padding.

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?

For a bulk-write tool with no output schema, the description covers capacity, ordering, backup, and overwrite semantics well. It stops short of saying what the call returns (count placed, per-block errors) or whether a failure leaves partial placement, which matters for a destructive bulk operation.

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%, so pos, block, data, dimension, and skip_backup are already documented in the schema. The description adds only the 10000 cap (duplicating maxItems) and the snapshot behavior that explains skip_backup indirectly; it adds no format or naming detail beyond the structured fields.

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 ("Places single blocks") plus a capacity bound, and the phrase "single blocks" implicitly contrasts with the region-oriented siblings like fill_blocks and copy_blocks. It does not name any sibling explicitly, so an agent must infer the boundary, but the core purpose is unambiguous.

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?

Usage is only implied: "single blocks" suggests this is for discrete placements rather than volume filling, which loosely points away from fill_blocks. There is no explicit when-to-use/when-not guidance, no mention of clear_blocks or undo as follow-ups, so the agent has to reason about the alternative itself.

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