Skip to main content
Glama

Create strange attractor

create_strange_attractor

Integrates ODE systems (Lorenz, Aizawa, Halvorsen) to create a strange-attractor geometry. Maintains a ring buffer of trail points, converts to polyline, thickens with Tube SOP for rendering, and returns controls summary.

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoContainer baseCOMP name.strange_attractor
parentNoParent network where the container is created./project1
attractorNoODE system to integrate: lorenz (classic butterfly), aizawa, or halvorsen.lorenz
trail_lengthNoPoints retained in the rolling ring buffer. Higher = longer ribbon, costlier SOP cook.
steps_per_frameNoRK-style integration sub-steps per cook frame (controls speed and smoothness).
dtNoIntegrator time step. Smaller = smoother but slower trajectory.
seedNoInitial state [x, y, z]. A tiny non-zero offset avoids the Lorenz fixed-point stall at the origin.
paramsNoOverride ODE constants. Lorenz: sigma, rho, beta. Aizawa: a, b, c, d, e, f. Halvorsen: a. Unknown keys are ignored.
thicknessNoTube SOP radius. Set to 0 to render the raw polyline (no Tube SOP — lighter on GPU).
colorNoConstant MAT colour (RGB, 0..1).
bg_colorNoRender TOP background colour (RGB, 0..1).
auto_frameNoAuto-position camera based on attractor bounding radius (deterministic; no live bound query).
expose_controlsNoExpose StepsPerFrame / Dt / TrailLength / Thickness as custom parameters on the container.
Behavior5/5

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

Discloses time-dependent behavior (pauses with timeline), component creation, pipeline details (Script CHOP, SOP, Tube SOP), and return format. 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?

Description is detailed but efficient relative to complexity; front-loaded with main action and well-structured, though slightly long.

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?

Covers purpose, usage, behavioral details, parameters, and return value (summary + JSON) adequately given 13 parameters and no output schema.

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?

Schema coverage is 100%, and description adds context for seed (avoids fixed-point stall) and params (lists ODE constants per system), going beyond 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?

Clearly states it builds a strange-attractor generator, specifies ODE systems (Lorenz/Aizawa/Halvorsen), and distinguishes from sibling tools by naming create_growth_system and create_particle_flock.

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 for when to use (deterministic CPU-geometry idiom) and a behavioral note about timeline pausing, but lacks explicit exclusions or detailed alternatives beyond the two mentioned siblings.

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