Skip to main content
Glama

Watch operator parameter changes

watch_parameter_changes

Subscribe to parameter change events on TouchDesigner operators. Use watch to register, unwatch to remove, and list to see active subscriptions.

Instructions

Opt-in: subscribe to param.changed events for an operator's parameters. When a watched parameter's value changes in TouchDesigner (by a human or a script), the bridge broadcasts a {path, par, prev, value, frame} event on the TD event stream, forwarded to the MCP client as a logging notification. Use action='watch' to register (optionally scoped to named parameters), 'unwatch' to remove, and 'list' to see active watches. Events only arrive when the server's TD event stream is enabled (TDMCP_EVENTS); param.changed is treated as a high-frequency event (coalesced bridge-side so a slider drag can't flood). Survives TDMCP_BRIDGE_ALLOW_EXEC=0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoOperator path to watch for parameter changes, e.g. /project1/level1. Required for action='watch'/'unwatch'; omit for action='list'.
actionNo'watch' registers a subscription, 'unwatch' removes it (or just the named parameters), 'list' returns all active watches.watch
parametersNoOptional list of parameter names to watch (e.g. ['opacity','level']). Omit to watch every parameter on the operator.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathNoThe canonical operator path (for watch/unwatch).
countNoNumber of active watches (for the 'list' action).
actionYesThe action that was performed: watch, unwatch, or list.
watchesNoEvery active watch (for the 'list' action).
watchingNoWhether an active watch remains on this op after the action.
parametersNoParameters now watched on this op, or null for a watch-all subscription.
Behavior5/5

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

The description adds significant value beyond annotations by detailing that events are high-frequency and coalesced, require the TD event stream to be enabled, and survive TDMCP_BRIDGE_ALLOW_EXEC=0. It also describes the event payload format, which annotations do not cover.

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 concise (~100 words) and well-structured: it starts with the core purpose, then usage, then caveats. Every sentence adds value with no wasted words.

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 tool's complexity (3 parameters, event streaming) and the presence of an output schema, the description covers all necessary aspects: subscription actions, scoping, event format, prerequisite (TDMCP_EVENTS), and high-frequency handling. No gaps remain.

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, the baseline is 3. The description adds meaning by explaining the interplay between parameters: 'path' is required for 'watch'/'unwatch' but not 'list', and 'parameters' optionally scopes the watch. This clarifies conditional usage beyond the schema's individual 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 it subscribes to `param.changed` events for an operator's parameters, using a specific verb (subscribe) and resource (operator parameters). It distinguishes itself from sibling tools like 'watch_node' by focusing on parameter changes and listing the three actions (watch, unwatch, list).

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 the tool (opt-in subscription) and provides context for when events are received (TDMCP_EVENTS enabled). It does not explicitly state when not to use it or compare to alternatives like 'watch_node' or 'animate_parameter', but the information is largely clear.

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