tdmcp

Create generative art

create_generative_art

Create evolving generative art in TouchDesigner by building a visual network with techniques like reaction-diffusion, GLSL, or noise, and control animation speed via a live knob.

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "technique": "<technique>"
    },
    "name": "create_generative_art"
  }
}

Input Schema

Name	Required	Description	Default
`technique`	Yes	Generative 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_path`	No	Parent network where the generative container is created (default '/project1').	/project1
`color_palette`	No	Free-text palette hint recorded in the result; best-effort, not all techniques honor it.
`evolution_speed`	No	Animation speed multiplier on the time uniform driving the look (1 = nominal, higher = faster evolution). Exposed as the 'Speed' knob.
`expose_controls`	No	When true (default), expose a live 'Speed' knob (evolution speed) on the system container.
`custom_glsl_code`	No	Fragment shader source used only when technique='custom_glsl'; if omitted, a default plasma shader is used (with a warning).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Discloses rich behavior beyond annotations: technique-specific implementation paths, fallback warnings, Speed knob exposure (except for recipe-built techniques), and the exact return structure including JSON block, errors, and inline preview. This far exceeds the annotation hints (readOnly=false, openWorld=true, destructive=false).

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 sentences, front-loaded with the core action, each sentence earning its place: what it creates, technique variations, and return value. No filler, appropriately sized for the tool's complexity.

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?

For a tool with 9 techniques, fallbacks, exposed controls, and a detailed return payload, the description fully covers creation behavior, technique limitations, knob behavior, and output structure. No output schema exists, but the description adequately compensates.

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 coverage is 100%, with detailed descriptions for all six parameters. The tool description largely repeats schema content (e.g., technique behavior and evolution_speed as the 'Speed' knob) without adding new parameter-level meaning, so the baseline 3 applies.

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?

Opens with a specific verb and resource: 'Create an evolving generative visual.' Clearly states it creates a baseCOMP under parent_path with specific generator structures and technique behaviors, distinguishing it from sibling create_* tools by covering multiple generative methods in one container.

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?

Provides context on when to use it by describing which techniques produce real GLSL vs fallback to animated noise (with warning). However, it does not explicitly name alternative tools for specialized techniques like create_reaction_diffusion, so it stops short of full exclusion guidance.

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

Deploy Server