Skip to main content
Glama

Create generative art

create_generative_art

Generate evolving generative visuals in TouchDesigner using techniques like reaction-diffusion, fractals, or custom GLSL shaders. Returns a network container, controls, and 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 real GLSL; custom_glsl uses your shader; 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).
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.
custom_glsl_codeNoFragment shader source used only when technique='custom_glsl'; if omitted, a default plasma shader is used (with a warning).
expose_controlsNoWhen true (default), expose a live 'Speed' knob (evolution speed) on the system container.
parent_pathNoParent network where the generative container is created (default '/project1')./project1
Behavior5/5

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

Discloses creation of nodes, fallback behavior for some techniques, exposure of Speed knob, and return value structure. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single paragraph is dense but efficiently communicates purpose, behavior, and return value. Could be slightly more structured but not overly verbose.

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 key aspects: creation, technique variations, controls, return value. Lacks details on error handling or prerequisites, but adequate given schema and annotations.

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?

While schema covers all parameters, the description adds technique-specific behavior (validated recipes, real GLSL, fallbacks) beyond basic schema descriptions.

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 evolving generative visual as a baseCOMP, and distinguishes it from many sibling create_* tools by specifying the output type and techniques.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool vs other create_* tools like create_glsl_shader or create_strange_attractor. Only intra-tool technique selection is hinted.

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