Skip to main content
Glama

Create voxel stack

create_voxel_stack

Turn any TOP into an isometric voxel stack: luminance drives column heights and colors, palette/height ramp modes and camera controls included. Uses animated noise if no TOP given.

Instructions

Isometric voxel-stack renderer driven by any TOP. Builds a single instanced Geometry COMP (boxSOP, N=cols·rows instances up to 256×256) with a CHOP chain sampling luminance for column height and per-instance color. Color modes: source_color (sample TOP directly), palette (Monument-Valley pastel ramp), height_ramp (same palette, height-based). Isometric ortho cam (rx=-35.264°, ry=45°) by default; perspective available. Exposes HeightScale, VoxelSize, and RotateY controls. If source_top_path is omitted, an animated noiseTOP drives the stack.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoBase name for the container (defaults to 'voxel_stack').
paletteNoRamp endpoints as [r,g,b] tuples (2–8 stops). Used only when color_mode='palette'. Defaults to a Monument-Valley pastel 5-stop ramp.
grid_sizeNoVoxel grid cols × rows. Hard-capped at 256×256 (65k instances).
color_modeNoPer-instance color: sample source TOP directly (source_color), look up into a palette ramp (palette), or use a default pastel height ramp (height_ramp).source_color
voxel_sizeNoCube edge length in world units; also the XZ spacing between voxels.
camera_modeNoIsometric uses ortho camera at rx=-35.264°, ry=45° (classic iso). Perspective uses a standard 35mm orbit cam.isometric
parent_pathNoParent network where the voxel stack container is created./project1
height_scaleNoMultiplier on luminance → Y translate. 0 = flat slab.
expose_controlsNoWhen true, expose HeightScale, RotateY, and VoxelSize knobs on the container.
source_top_pathNoPath to an existing TOP that drives heights and colors. If omitted, a built-in animated noiseTOP feeds the stack.
output_resolutionNoRender TOP resolution [width, height].
Behavior5/5

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

Exceeds annotation signals by detailing internal construction (boxSOP, N=256x256 instances), color modes, camera defaults, exposed controls, and fallback to animated noiseTOP. This is rich context beyond the readOnly/destructive flags.

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?

Four sentences, information-dense, front-loaded with the core purpose. No fluff.

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?

Covers the tool's behavior thoroughly: build method, limits, color modes, camera, controls, and default source. For a creation tool without output schema, this is sufficient.

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 covers 100% of parameters with descriptions. The description does not add new parameter meaning; it summarizes color modes and controls already enumerated in the schema. Baseline 3 is appropriate.

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?

States a specific verb+resource: 'Isometric voxel-stack renderer driven by any TOP' and describes construction details (instanced Geometry COMP, CHOP chain). Clearly distinguishes from sibling create_3d_scene or create_geo_visualization by focusing on voxel-stack rendering.

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?

Implied usage from the description but no explicit when-to-use vs alternatives. It notes TOP-driven input and default noise TOP, which gives context, but doesn't name alternative tools or exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucasmaher-hash/touch-designer-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server