Skip to main content
Glama

Erase region

goxel_erase_region
Destructive

Remove voxels within a specified box or shape, optionally filtering by color, to edit or clean up 3D models.

Instructions

Remove the voxels in a region (min/max box and/or shape), optionally only the ones of a given color. Can be undone with goxel_undo.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "goxel_erase_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNoLayer name or id (default: the active layer)
regionNoRegion: a min/max box and/or a shape
toleranceNoRGB tolerance (sum of the channel differences)
all_layersNo
color_filterNoOnly erase voxels of this color

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, so the lower bound is met; the description adds genuinely new context by naming the undo path for recoverability. It does not explain scope implications such as whether omitting region erases the whole layer or what all_layers does, leaving some risk undisclosed.

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 compact sentences, with the core action front-loaded and the undo note as secondary. No filler.

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

Completeness3/5

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

For a destructive tool with zero required parameters and a deeply nested shape schema, the description should say what happens when region/color_filter are omitted (erase whole layer? active layer only?) and how layer vs all_layers interact. Those gaps matter more than the return value, which no output schema exists to cover.

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 80%, so the schema does most of the work; the description restates the min/max box plus shape and the color restriction but adds nothing on tolerance, layer/all_layers, or the interaction between box and shape beyond what the schema already says.

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 ('Remove the voxels in a region') plus the optional color restriction, which points to erase semantics rather than the sibling recolor/add tools. It stops short of explicitly differentiating itself from goxel_recolor_region or goxel_add_voxels by name.

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?

'Can be undone with goxel_undo' gives a recovery path and the color filter hints at a narrower use case, but there is no explicit when-to-use/when-not guidance or a named alternative for color-only operations (goxel_recolor_region exists and is not mentioned).

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