Skip to main content
Glama

Set block

set_block
DestructiveIdempotent

Place a single block at specified X, Y, Z coordinates, replacing any existing block, with optional block state and NBT data.

Instructions

Place one block, replacing what is there. For more than a handful of blocks use fill_region or build_from_layers. Doors and beds need both halves placed explicitly.

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

Input Schema

NameRequiredDescriptionDefault
xYesBlock X coordinate (east is +X).
yYesBlock Y coordinate (height; the overworld build range is -64 to 319).
zYesBlock Z coordinate (south is +Z).
nbtNoBlock-entity data. The plugin applies only CustomName (containers) and Text1-Text4 (sign lines); other keys are ignored.
blockYesBlock id such as 'minecraft:stone' or 'oak_planks' (the minecraft: namespace is optional).
block_stateNoBlock state properties, e.g. {'facing': 'north'}. Handled specially: facing (north/south/east/west/up/down), axis (x/y/z), half (top/bottom - also for doors and tall plants), shape (stairs: straight/inner_left/inner_right/outer_left/outer_right), rotation (signs, banners, heads: a compass direction such as north_north_east, not 0-15), waterlogged/open/powered (true/false). Any other vanilla property also works (e.g. type=top for slabs, hinge=left, lit=true).

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 destructiveHint=true and idempotentHint=true, so the safety profile is carried by structured data; the description reinforces it with "replacing what is there" and adds a genuinely non-obvious constraint that doors and beds require both halves to be placed explicitly.

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 short sentences, action first, alternatives second, caveat last — nothing redundant and no wasted words.

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?

An output schema exists and annotations cover safety, so the description only needs the core semantics and routing, which it supplies; it stops short of noting coordinate-range failures or what happens with invalid block ids, a minor gap for a mutating single-block 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 coordinates, block ids, block_state handling, and the NBT plugin limitations, so the description adds no parameter detail beyond it; 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?

"Place one block, replacing what is there" gives a specific verb and resource plus the replacement semantics, which immediately separates it from the bulk siblings fill_region and build_from_layers.

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?

Explicit routing: "For more than a handful of blocks use fill_region or build_from_layers" tells the agent when to pick an alternative, and the door/bed caveat warns about a case where this tool alone is insufficient.

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