Skip to main content
Glama

TD Set Parameter (live)

td_set_parameter

Set a parameter on a TouchDesigner operator in real time by providing a constant value, a Python expression, or pulsing a trigger parameter.

Instructions

Set a parameter on an operator in a running TouchDesigner instance (live control via the td_mcp bridge). Drives the documented op.par.NAME.val (value), op.par.NAME.expr (expr) and op.par.NAME.pulse() members. parameter may be a documented label (e.g. 'Period') or an exact parameter name (e.g. 'period'); labels are resolved via the operator map. Provide exactly one of value, expr, or pulse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
exprNoPython expression to bind (sets op.par.NAME.expr), e.g. 'absTime.seconds'. Use this OR value OR pulse.
pathYesFull path of the operator whose parameter is set, e.g. '/td_mcp/sandbox/noise1'.
pulseNoWhen true, pulses the parameter (calls op.par.NAME.pulse()), used for momentary/trigger parameters like 'Reset'. Use this OR value OR expr.
valueNoConstant value to assign (sets op.par.NAME.val). Use this OR expr OR pulse.
parameterYesParameter to set. Either a documented label (e.g. 'Period') or an exact parameter name (e.g. 'period'). Labels are resolved to the parameter name via the operator map; correct names pass through.
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains the behavioral traits (drives specific members, live control) but does not disclose potential side effects, required permissions, or reversibility. Adequate but not comprehensive.

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?

The description is concise (two main sentences plus a continuation) and front-loaded with the core purpose. Every sentence adds value, though it could be slightly more streamlined without losing information.

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?

Given the tool's complexity (5 parameters, mutual exclusivity, label resolution) and no output schema, the description provides sufficient context to use the tool effectively. It covers parameter usage, required fields, and the effect on the operator.

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% with all parameters described. The description adds significant meaning beyond the schema: it clarifies the mutual exclusivity of value/expr/pulse, explains that parameter can be a label or exact name, and describes the underlying member access. This provides useful context for proper invocation.

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 clearly states it sets a parameter on an operator in a running TouchDesigner instance for live control. It specifies the internal members affected (val, expr, pulse) and distinguishes from sibling tools by focusing on parameter mutation rather than retrieval or other operations.

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 explicit guidance on mutual exclusivity of value/expr/pulse and describes how parameter labels are resolved. While it does not mention when to use this tool over alternatives, the context of the tool (live parameter setting) is clear from the title and description.

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/bottobot/touchdesigner-mcp-server'

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