Skip to main content
Glama

Create generative art

create_generative_art

Create evolving generative visuals in TouchDesigner. Generates a node network with a chosen technique (noise, reaction-diffusion, GLSL, etc.) and returns paths, controls, and a preview.

Instructions

Create an evolving generative visual. Creates a new baseCOMP under parent_path holding the generator (a recipe network, a GLSL TOP + Text DAT, or a noise chain) ending in a Null output. reaction_diffusion/noise_landscape use validated recipes; strange_attractor, voronoi, and fractal render built-in GLSL; custom_glsl accepts caller shader source only when TDMCP_RAW_PYTHON=on and TDMCP_BRIDGE_ALLOW_EXEC=1; the rest fall back to animated noise (with a warning). Exposes a live 'Speed' knob (except for recipe-built techniques). Returns a summary plus a JSON block with the container path, created node paths, the output path, exposed controls, the technique, any node errors, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
techniqueYesGenerative method. reaction_diffusion/noise_landscape build validated recipes; strange_attractor/voronoi/fractal render faithful inline GLSL; custom_glsl uses your shader (custom_glsl_code); l_system/cellular_automata/flow_field currently fall back to an animated-noise approximation (with a warning).
parent_pathNoParent network where the generative container is created (default '/project1')./project1
color_paletteNoFree-text palette hint recorded in the result; best-effort, not all techniques honor it.
evolution_speedNoAnimation speed multiplier on the time uniform driving the look (1 = nominal, higher = faster evolution). Exposed as the 'Speed' knob.
expose_controlsNoWhen true (default), expose a live 'Speed' knob (evolution speed) on the system container.
custom_glsl_codeNoFragment shader source used only when technique='custom_glsl'; if omitted, a default plasma shader is used (with a warning).
Behavior4/5

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

Annotations indicate a mutating (readOnlyHint=false) but non-destructive operation. The description adds important behavioral details: it creates a baseCOMP with specific generator types, exposes a live Speed knob except for recipe-built techniques, and returns a structured JSON summary. It also discloses fallback behavior and the env-var prerequisite for custom_glsl.

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?

Three dense sentences, front-loaded with the core purpose. Each clause adds value: the container structure, technique handling, knob behavior, and the return summary. No filler or repetition.

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?

Covers purpose, per-technique behavior, environmental constraints for custom_glsl, and the full return contract (summary plus JSON with specific fields) despite no output schema. Lacks explicit guidance on alternatives relative to sibling tools, which is a completeness gap given the extensive sibling list.

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 description coverage is 100%, with each of the six parameters already documented. The description adds high-level technique behavior (validated recipes vs built-in GLSL vs fallback) that enriches the 'technique' enum, but doesn't provide parameter syntax/format details beyond 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?

Description clearly states it 'Creates a new baseCOMP under parent_path' holding a generative generator with explicit structure (recipe network, GLSL TOP + Text DAT, or noise chain) ending in a Null output. The technique enumeration and output contract distinguish it from sibling creation 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 conditional usage context: custom_glsl only works when TDMCP_RAW_PYTHON=on and TDMCP_BRIDGE_ALLOW_EXEC=1, unsupported techniques fall back to noise with a warning, and recipe-built techniques don't get the Speed knob. It does not explicitly name alternative sibling tools or state when to choose this over others like create_glsl_shader.

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