Skip to main content
Glama

td_set_params

DestructiveIdempotent

Set static or live expression values on TouchDesigner node parameters. Supports static values, reactive expressions, resets, and explicit modes.

Instructions

Set node parameters (static values or live expressions).

Parameter-semantics checks are advisory here by default (param_semantics_policy= 'warn'): findings are attached but the write proceeds, since some out-of-range values are legitimate in TD (e.g. extending a soft UI range). Use param_semantics_policy='block', or the brain/transaction path which gates automatically, when you want invalid bindings to stop the write.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesAbsolute node path
paramsYesDictionary of parameter names to values. Supports five modes: • Static value (plain): {'seed': 42, 'colorr': 1.0} • Expression (reactive, updates every frame): {'seed': {'expr': 'absTime.seconds * 10'}, 'tx': {'expr': "op('noise1')['chan1']"}} • Explicit static: {'seed': {'val': 42}} • Reset to default: {'seed': {'reset': true}} — resets value and clears expression • Clear expression: {'seed': {'mode': 'constant', 'val': 42}} — force constant mode Expressions make networks ALIVE — use them for anything that should move, react, or change over time.
include_hintsNoIf True, attach a ``hints`` block via td_get_hints. Auto-injection still fires when the params dict assigns a string to a reference-style parameter (instanceop/material/camera/lights/geometry/top/chop/sop/dat/comp).
param_semantics_policyNoDocs-grounded parameter safety policy for direct writes. 'warn' (default) preserves normal direct-tool behavior with attached findings — the write PROCEEDS even on invalid enum / out-of-range / bad op-reference; 'block' refuses the write before mutation when parameter semantics find invalid, unknown, or high-risk bindings. NOTE: this direct path is advisory by default. The brain/transaction path (td_brain_plan → td_brain_execute) HARD-FAILS the same contract violations. Pass 'block' here for equivalent strictness on direct writes.warn

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description details the behavior of parameter-semantics checks (advisory by default, but attach findings) and notes that some out-of-range values are legitimate. It also explains the expression modes and their impact ('make networks ALIVE'). This adds context beyond annotations (destructiveHint, idempotentHint) without contradiction.

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 front-loaded with a clear purpose, then efficiently explains modes and policy. Every sentence adds value, and the structure logically progresses from general to specific. It is appropriately concise for the complexity of the tool.

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 output schema exists (covering return values), the description focuses on input parameters and behavior, which it covers thoroughly. It addresses modes, policy, and integration with other tools (brain/transaction path), making it complete for an agent to select and invoke this tool correctly.

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%, so baseline is 3. The description adds significant meaning by explaining the five modes for params (static, expression, explicit static, reset, clear expression) with examples, and details the include_hints and param_semantics_policy parameters, providing context not fully captured in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Set node parameters (static values or live expressions)', clearly indicating the action and resource. It adds detail about static vs. live expressions, but does not explicitly differentiate from siblings like td_set_param_bounds, though the tool name and context make the purpose distinct.

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 explains when to use different param_semantics_policy values ('warn' vs 'block') and contrasts with the brain/transaction path. It provides clear context for the default advisory behavior and when to enforce strictness, but doesn't explicitly state when to use this tool over other parameter-related tools.

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/dreamrec/TDPilot'

If you have feedback or need assistance with the MCP directory API, please join our Discord server