Skip to main content
Glama

Create preset morph

create_preset_morph

Snapshot any TouchDesigner operator's animatable parameters into named slots, then blend between them with weighted crossfades or single A↔B recall via Lag CHOP and Lookup curve.

Instructions

Target-agnostic preset morph engine: snapshot any OP's animatable parameters into N named slots, then blend between them with a weight vector (or a single A↔B recall) through a Lag CHOP + Lookup curve, exposing the live blended values on a Null CHOP for bind_to_channel consumers. Unlike create_look_bank (which is scoped to a control COMP's custom pars with a 2-slot A↔B knob), this drives any OP and supports >2 simultaneous weights (normalized internally). Reuses manage_cue's MORPH_HOOK for beat/bar quantized recall. Note: Lag CHOP does not advance while the timeline is paused.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNobuild: create the morph container. store: snapshot the target's animatable parameters into a named slot. recall: snap or crossfade the target to one slot. set_weights: drive an N-way weighted blend across all stored slots (vector is clipped to >=0 and normalized). list / delete slots.build
parent_pathNoParent COMP where the morph container is built./project1
nameNoName of the morph container (baseCOMP) created inside parent_path.preset_morph
target_pathNoThe node whose parameters are snapshotted and driven (required for build/store). Any OP with animatable numeric/toggle/menu pars.
includeNo(store) Restrict the snapshot to these parameter names (tuplet names like 'tx', 'feedback'). Omit to capture every animatable numeric/toggle/menu parameter (pulses, strings, file refs are always skipped).
slotNoSlot name (required for store / recall / delete).
weightsNo(set_weights) Map of slot-name -> weight. Negatives clipped to 0; the vector is normalized internally (sum -> 1) before lerp. Missing slots default to 0.
morph_secondsNo(recall) 0 = snap; >0 = ease to slot over this many seconds via a Lag CHOP on the weight vector. Note: Lag CHOP does not advance while the timeline is paused.
quantizeNo(recall) Defer the snap/crossfade to the next musical boundary (project tempo). Mirrors manage_cue / create_look_bank.off
interpolationNoInterpolation curve applied to each parameter when crossfading. linear is a straight lerp; cosine/cubic shape the lagged weights through a Lookup CHOP curve.linear
Behavior4/5

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

Discloses key behaviors: Lag CHOP doesn't advance while timeline paused, weight vector is normalized internally, interpolation curves via Lookup CHOP. No annotation contradiction, as readOnlyHint=false and destructiveHint=false align with the description. Minor omission: doesn't specify if the tool overwrites existing containers.

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?

Single paragraph, densely packed with essential information. Front-loads the core purpose and comparison. No redundancy; every sentence earns its place.

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 the complexity (10 params, nested objects, action enum), the description provides a comprehensive overview of the morph engine's lifecycle (build, store, recall, set_weights, list, delete) and edge cases (Lag CHOP pause). No output schema needed.

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?

With 100% schema coverage, baseline is 3. Description adds significant value by explaining how parameters interact (e.g., normalization, Lag CHOP behavior, interpolation curves) and the overall morph engine architecture.

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 target-agnostic preset morph engine, snapping any OP's animatable parameters into named slots and blending with weight vectors. It distinguishes itself from create_look_bank by noting it drives any OP and supports >2 weights.

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

Usage Guidelines5/5

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

Explicitly contrasts with create_look_bank, stating when to use this tool (any OP, >2 weights) and when not (limited to control COMP with 2-slot A↔B). Also mentions reuse of manage_cue's MORPH_HOOK for quantized recall.

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