Skip to main content
Glama

Clear an area to air

clear_blocks
DestructiveIdempotent

Set every block in a box to air, emptying containers without drops and optionally removing entities, with an undo snapshot. Use it to clear a defined Minecraft area.

Instructions

Sets every block in the box to air (containers are emptied, nothing drops). With include_entities (default on) it also removes the entities in the box first, without drops; players are never touched. Snapshots the area, entities included, for undo.

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

Input Schema

NameRequiredDescriptionDefault
toYesThe opposite corner [x, y, z], inclusive
fromYesOne corner [x, y, z]
confirmNoSet true only after the person agreed to this change (needed while confirmDestructive is on).
dimensionNoDimension. Default overworld.overworld
skip_backupNoOnly for areas too big for an undo snapshot, after backup_world. Default false.
include_entitiesNoInclude entities (item frames, paintings, armor stands, mobs, minecarts, boats). Default: includeEntities in the config (on).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds substantive behavior: containers are emptied rather than dropped, entities (item frames, paintings, mobs, minecarts, boats) are removed without drops, players are never affected, and the area is snapshotted for undo. That is exactly the consequence-level detail an agent needs before a destructive call.

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 sentences, front-loaded with the destructive effect, then the entity behavior and undo snapshot. Every clause carries information and nothing is padded.

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 destructive, no-output-schema tool, the description covers the mutation's scope, the player-safety guarantee, the entity side effect, and the undo snapshot — combined with annotations declaring destructiveness and idempotency, an agent can call it correctly.

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 from/to, dimension, confirm, skip_backup and include_entities are already documented. The description restates include_entities' default and its entity list, but adds little for the other parameters beyond what the schema says, so baseline 3 applies.

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?

The description names a specific verb and effect: 'sets every block in the box to air,' with concrete detail that containers are emptied and nothing drops. That implicitly separates it from fill_blocks/copy_blocks, though no sibling is named explicitly, which keeps it short of a 5.

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 supplies real preconditions: confirm should be set only after a person agreed (while confirmDestructive is on), and skip_backup only for areas too big for an undo snapshot, after backup_world. There is no explicit when-to-use-this-instead-of-X guidance (e.g. vs undo or fill_blocks), so it stops short of a 5.

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