Skip to main content
Glama

Create fluid sim

create_fluid_sim

Build a real-time 2D fluid/ink/dye simulation in TouchDesigner using semi-Lagrangian advection and Jacobi pressure solve. Supports auto, mouse, or audio-driven injection with artist controls for viscosity and dissipation.

Instructions

Build a real-time 2D fluid/ink/dye simulation (stable-fluids style: semi-Lagrangian advection + Jacobi pressure solve + gradient-subtract projection + dye advection) as a stack of GLSL TOPs in feedback loops inside a new baseCOMP under parent_path. Exposes artist-facing controls (dye color, injection radius/strength, viscosity, dissipation, pressure iterations, inject U/V) and optionally binds a CHOP at audio_path so audio drives the dye injection strength. With injection_mode='auto', a slow LFO drives the splat point so the sim shows life with no input. Returns a summary plus a JSON block with the container path, created node paths, the dye_out output path, exposed controls, any node errors, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
resolutionNoSim grid resolution (square). 512 is safe on integrated GPUs.512
dye_colorNoInjected dye color as a '#rrggbb' hex string.#ff3a8c
injection_radiusNoRadius of the dye/force splat in UV units (0.01–0.5).
injection_strengthNoMultiplier on dye + velocity splat per frame (0–2).
viscosityNoVelocity dissipation per frame (0–1). Higher = thicker fluid.
dissipationNoDye decay per frame (0.9–1.0). <1 fades trails.
pressure_iterationsNoJacobi iterations per frame (1–60). Higher = more incompressible.
injection_modeNoHow the splat point/strength is driven.auto
audio_pathNoOptional CHOP path; channel 0 multiplies injection strength when set.
expose_controlsNoAuto-expose an artist-facing control panel on the container.
parent_pathNoParent network where the fluid_sim container is created./project1
Behavior4/5

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

Annotations indicate readOnlyHint=false (write operation) and destructiveHint=false; description confirms creation of nodes without destruction, adds detailed behavioral context (simulation method, controls, audio binding). No contradictions.

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 well-structured and front-loaded with purpose, but is somewhat long. However, every sentence adds value given the tool's complexity. Could be slightly more concise.

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?

With 11 parameters and no output schema, the description covers the tool's behavior, output format (summary + JSON), and optional features. Lacks explicit error handling but otherwise comprehensive.

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 has 100% parameter description coverage, so baseline is 3. Description mentions some parameters (dye color, injection radius, etc.) but does not add significant new meaning beyond the schema's own 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 a real-time 2D fluid simulation using stable-fluids techniques, exposing artist controls. It distinguishes itself from sibling create tools (e.g., create_particle_system) by specificity to fluid/ink/dye sim.

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

Usage Guidelines3/5

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

The description implies usage (when you need a fluid sim) but does not explicitly say when to use vs alternatives or when not to use. No exclusion criteria or context is provided.

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