Skip to main content
Glama

Recolor

goxel_recolor_region

Recolor existing voxels in a chosen region or matching a source color, such as changing gray rims to black. Set the target color and optionally limit by layer, region, or tolerance.

Instructions

Change the color of existing voxels in a region and/or of a given color (for example: gray rims -> black).

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": {
      "to_color": "<to_color>"
    },
    "name": "goxel_recolor_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
layerNoLayer name or id (default: the active layer)
regionNoDefault: the whole layer
to_colorYesColor: "#rrggbb", "#rrggbbaa", [r,g,b] / [r,g,b,a] (0-255) or a name (black, white, red, darkred, green, darkgreen, blue, darkblue, lightblue, yellow, orange, amber, purple, pink, brown, gray, grey, darkgray, darkgrey, lightgray, lightgrey, silver, chrome, gold, cyan, magenta, glass, tinted)
toleranceNo
all_layersNo
from_colorNoOnly recolor voxels of this color

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. Saying 'existing voxels' usefully discloses that no new geometry is created, which is meaningful for a mutation. But it says nothing about undo behavior, permissions, what happens to non-matching voxels, or how tolerance/all_layers affect the result — significant gaps for an unannotated mutation tool.

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?

A single well-formed sentence with an illustrative example in parentheses; scoping (region and/or color) is front-loaded and every phrase earns its place.

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 mutation tool with no annotations, no output schema, and a nested region shape, the description is only partially complete. It omits the meaning and effect of tolerance and all_layers and gives no hint about the return or error behavior, leaving an agent to infer behavior from the schema alone.

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 67%, so several parameters (region, from_color, to_color) are already well described in the schema. The description adds the 'region and/or given color' mapping but does not mention tolerance or all_layers, both of which are undocumented in the schema and left without any semantic explanation in the description.

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+resource: change the color of existing voxels, scoped to a region and/or a source color. This clearly distinguishes it from siblings like goxel_add_voxels, goxel_erase_region and goxel_draw_primitive (which create/remove/place geometry rather than recolor existing voxels). It does not explicitly name any sibling, so 4 rather than 5.

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?

The parenthetical 'gray rims -> black' gives a concrete example of intended use, implicitly signaling when to reach for this tool. However, there is no explicit when-to-use vs alternatives guidance and no statement about cases where you would instead add/erase/draw.

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