Skip to main content
Glama

Create Shader Park sculpture

create_shader_park

Compiles Shader Park JavaScript code into a TouchDesigner GLSL MAT scene with live control parameters.

Instructions

Compile Shader Park JavaScript sculpture code with shader-park-core and instantiate it as a self-contained TouchDesigner GLSL MAT scene with live controls. Use the companion shader-park:tox script when you specifically want the official Shader Park .tox plugin workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoShader Park sculpture code. Example: `let size = input(); sphere(size);`. The code is compiled with shader-park-core and stored in a Text DAT for editing.setMaxIterations(96); rotateY(time * 0.25); color(vec3(0.2, 0.8, 1.0)); sphere(0.45);
nameNoName of the created baseCOMP container.shader_park_sculpture
scaleNoInitial `_scale` uniform value.
speedNoAnimation speed multiplier for the Shader Park `time` uniform.
opacityNoInitial opacity uniform value.
camera_zNoCamera distance from the sculpture.
step_sizeNoInitial Shader Park raymarch stepSize uniform value.
resolutionNoRender TOP resolution [width, height].
parent_pathNoParent COMP path for the new sculpture./project1
uniform_valuesNoInitial values for Shader Park `input()` uniforms by name, e.g. `{ "size": 0.55 }`.
expose_controlsNoExpose Speed / Scale / Opacity / StepSize / CameraZ plus any float Shader Park inputs.
Behavior4/5

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

Annotations already indicate the tool is not read-only and not destructive. The description adds context that the tool creates a self-contained scene with live controls, clarifying the side effect of creating nodes. It does not explain details like overwriting behavior, but given the annotations, the disclosure is adequate.

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 primary action, and the second sentence provides a clear alternative. No wasted words.

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

Completeness4/5

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

For a tool with 11 parameters and no output schema, the description covers the high-level purpose and primary alternative. It could mention the return value or how to access the created scene, but given the rich schema, it is sufficiently complete.

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?

The schema has 100% coverage with detailed descriptions for all 11 parameters, so the description does not need to add parameter details. It provides general context about compiling code and instantiation, but no parameter-specific meaning beyond the schema.

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 a specific action: compiling Shader Park JavaScript code and instantiating it as a self-contained TouchDesigner GLSL MAT scene. It distinguishes this tool from the companion shader-park:tox script and other shader tools by specifying the self-contained scene and live controls.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly notes to use the companion shader-park:tox script when the official plugin workflow is desired, providing a clear exclusion. The description implies this tool is for the alternative self-contained approach, giving context for when to choose it over the sibling.

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