Skip to main content
Glama

Create voxel stack

create_voxel_stack

Build a voxel stack visualization driven by any TOP: luminance sets column height and per-instance color, with isometric or perspective camera.

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
parent_pathNoParent network where the voxel stack container is created./project1
nameNoBase name for the container (defaults to 'voxel_stack').
source_top_pathNoPath to an existing TOP that drives heights and colors. If omitted, a built-in animated noiseTOP feeds the stack.
grid_sizeNoVoxel grid cols × rows. Hard-capped at 256×256 (65k instances).
voxel_sizeNoCube edge length in world units; also the XZ spacing between voxels.
height_scaleNoMultiplier on luminance → Y translate. 0 = flat slab.
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
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.
output_resolutionNoRender TOP resolution [width, height].
camera_modeNoIsometric uses ortho camera at rx=-35.264°, ry=45° (classic iso). Perspective uses a standard 35mm orbit cam.isometric
expose_controlsNoWhen true, expose HeightScale, RotateY, and VoxelSize knobs on the container.
Behavior4/5

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

Given annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description adds value by disclosing creation details (instanced Geometry COMP, CHOP chain, hard-caps at 256x256) and structural constraints, which goes beyond the annotation hints.

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?

The description is concise yet comprehensive, front-loading the purpose and providing key details in two paragraphs. Every sentence contributes meaningful information without redundancy.

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?

With 11 parameters, full schema, and no output schema, the description covers essential aspects: creation process, parameter meanings, defaults, constraints (256x256 cap), and behavior. It leaves no critical gaps for an agent to misunderstand.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds context by explaining parameter behaviors (e.g., color modes, camera modes, expose_controls) and defaults, making the tool more understandable.

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?

The description clearly states the tool creates an isometric voxel-stack renderer driven by a TOP, with details on how it builds geometry and color modes. This specific verb+resource description distinguishes it from sibling 'create_*' tools.

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?

The description provides clear usage context (e.g., 'If source_top_path is omitted, a built-in animated noiseTOP drives the stack'), but does not explicitly mention when not to use this tool or name alternative tools. It implies usage scenarios effectively.

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/Pantani/tdmcp'

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