Skip to main content
Glama

td_create_node

Destructive

Add any TouchDesigner operator type to a parent path, with custom name and position.

Instructions

Create a new TouchDesigner operator of a given type under a parent path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoCustom name for the new node. If None, TD assigns a default name.
nodeXNoHorizontal position in the network editor (pixels). Use multiples of 200 for clean spacing between nodes.
nodeYNoVertical position in the network editor (pixels). Use multiples of 200 for clean spacing between rows.
node_typeYesTouchDesigner operator type to create. Examples: TOPs: 'noiseTOP', 'levelTOP', 'nullTOP', 'compositeTOP', 'feedbackTOP', 'moviefileinTOP' | CHOPs: 'waveCHOP', 'noiseCHOP', 'nullCHOP', 'mathCHOP', 'constantCHOP', 'selectCHOP' | SOPs: 'sphereSOP', 'boxSOP', 'gridSOP', 'lineSOP', 'nullSOP', 'transformSOP', 'noiseSOP' | DATs: 'textDAT', 'tableDAT', 'scriptDAT', 'nullDAT', 'selectDAT', 'chopexecDAT' | COMPs: 'baseCOMP', 'containerCOMP', 'geometryCOMP', 'cameraCOMP', 'lightCOMP' | MATs: 'pbrMAT', 'phongMAT', 'wireframeMAT', 'constMAT'
parent_pathNoPath to the parent COMP where the node will be created/project1
include_hintsNoIf True, attach a ``hints`` block sourced from td_get_hints for the chosen op_type. Auto-injection still fires for high-risk op_types (feedbackTOP, glslTOP, geometryCOMP, …) regardless of this flag.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description only adds the creation action, without explaining side effects (e.g., behavior if node exists, error handling). Adequate but no extra transparency.

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 sentence, no fluff, efficient. Contains all essential elements (verb, resource, scope).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having output schema and annotations, the description lacks context on return value, error handling, or behavior for edge cases like invalid parent path. Adequate but not fully complete.

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 coverage is 100%, and the description adds no additional meaning beyond the schema. Baseline 3 is appropriate since schema already explains parameters well.

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 verb (create), resource (TouchDesigner operator), and scope (under a parent path). It distinguishes from sibling tools like td_delete_node, td_copy_node, etc.

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

Usage Guidelines2/5

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

No guidance on when to use vs alternatives. The description does not mention prerequisites, when not to use, or compare with similar tools like td_copy_node.

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