tdmcp

Create strange attractor

create_strange_attractor

Generate a 3D strange attractor in TouchDesigner by integrating Lorenz, Aizawa, or Halvorsen ODE systems, with configurable parameters and an automatic render pipeline.

Instructions

Build a strange-attractor deferred geometry generator: a Script CHOP integrates a chosen ODE system (Lorenz / Aizawa / Halvorsen) with configurable sub-steps and maintains a rolling ring buffer of trail_length points. A Script SOP converts the channels into one open polyline; an optional Tube SOP thickens it for shaded render inside a Geometry COMP + Camera + Light + Render TOP pipeline. Closing Roadmap Milestone 4. Complements create_growth_system (L-systems) and create_particle_flock (boids) as the deterministic CPU-geometry idiom. With TD timeline paused the integrator pauses too (time-dependent) — resume playback to continue. Returns a summary plus a JSON block with the container path, output path, exposed controls, errors, warnings, and an inline preview.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_strange_attractor"
  }
}

Input Schema

Name	Required	Description	Default
`dt`	No	Integrator time step. Smaller = smoother but slower trajectory.
`name`	No	Container baseCOMP name.	strange_attractor
`seed`	No	Initial state [x, y, z]. A tiny non-zero offset avoids the Lorenz fixed-point stall at the origin.
`color`	No	Constant MAT colour (RGB, 0..1).
`params`	No	Override ODE constants. Lorenz: sigma, rho, beta. Aizawa: a, b, c, d, e, f. Halvorsen: a. Unknown keys are ignored.
`parent`	No	Parent network where the container is created.	/project1
`bg_color`	No	Render TOP background colour (RGB, 0..1).
`attractor`	No	ODE system to integrate: lorenz (classic butterfly), aizawa, or halvorsen.	lorenz
`thickness`	No	Tube SOP radius. Set to 0 to render the raw polyline (no Tube SOP — lighter on GPU).
`auto_frame`	No	Auto-position camera based on attractor bounding radius (deterministic; no live bound query).
`trail_length`	No	Points retained in the rolling ring buffer. Higher = longer ribbon, costlier SOP cook.
`expose_controls`	No	Expose StepsPerFrame / Dt / TrailLength / Thickness as custom parameters on the container.
`steps_per_frame`	No	RK-style integration sub-steps per cook frame (controls speed and smoothness).

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?

Annotations already indicate readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds substantial behavioral context beyond this: time-dependent integration, rolling ring buffer, optional Tube SOP, deterministic CPU-geometry idiom, and exact return fields including 'errors, warnings, and an inline preview.' There is no contradiction with the annotations.

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 about 100 words and densely informative. It covers the architecture, rendering pipeline, relationship to sibling tools, critical temporal behavior, and return value format without fluff. Each sentence adds value, and the main action is front-loaded.

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?

Given 13 parameters with complete schema descriptions, solid annotations, and no output schema, the description compensates well. It explains the full pipeline (CHOP -> SOP -> Tube -> render), the deterministic CPU-geometry context, timeline sensitivity, and exactly what the tool returns (summary plus JSON block with container path, output path, controls, errors, warnings, inline preview). This is comprehensive for an agent to select and invoke correctly.

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 input schema has 100% coverage with all parameters described in detail, including defaults, bounds, and specific meanings (e.g., dt, trail_length, attractor). The description only briefly mentions 'configurable sub-steps' and 'trail_length' without adding new semantic depth beyond the schema. With full schema coverage, the baseline of 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?

The description clearly states its purpose: 'Build a strange-attractor deferred geometry generator' with specific implementation details (Script CHOP, Script SOP, optional Tube SOP). It distinguishes itself from sibling tools by explicitly naming create_growth_system and create_particle_flock as complements, making it clear what this tool does and how it relates to others.

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 context and alternatives: 'Complements create_growth_system (L-systems) and create_particle_flock (boids) as the deterministic CPU-geometry idiom.' It also notes time-dependent behavior ('With TD timeline paused the integrator pauses too'), which helps the agent decide when this tool is appropriate. However, it does not explicitly state when not to use it, so it stops short of a 5.

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

Deploy Server