Skip to main content
Glama
Sign In
TouchDesigner MCP

TouchDesigner MCP

by 8beeeaaat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_td_node

Creates a new node in a TouchDesigner project at a specified parent path, using a given node type. Add components programmatically to automate project structure changes.

Instructions

Create a new node in TouchDesigner

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "parentPath": "<parentPath>",
      "nodeType": "<nodeType>"
    },
    "name": "create_td_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodeNameNoName of the new node (optional)
nodeTypeYesType of the node to create (e.g., textTop)
parentPathYesPath to the parent node (e.g., /project1)
detailLevelNoResponse detail level for tool output (minimal, summary, or detailed)
responseFormatNoStructured output format for formatted responses

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv1.4.11

TDQS

C2.9/5.0
Behavior2/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 only restates the mutation ('Create a new node') and omits side effects, naming/collision behavior, persistence, required connection state, or response format. This is not misleading but is too sparse to be transparent.

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 a single, front-loaded sentence with no filler or redundancy. However, it is so minimal that its brevity comes at the cost of valuable usage and behavioral context.

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

Completeness2/5

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

For a mutating tool with no annotations and no output schema, the description is incomplete: it doesn't mention the required parent/type relationship beyond the schema, expected output, or when to use it. The tool has 5 parameters and 12 siblings, yet the description provides no context to disambiguate invocation.

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?

The input schema has 100% description coverage, so the baseline applies even though the tool description says nothing about parameters. The schema already documents parentPath, nodeType, nodeName, detailLevel, and responseFormat. No additional parameter meaning is added by the description.

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 the operation: 'Create a new node in TouchDesigner.' It distinguishes itself from sibling tools like delete_td_node and get_td_nodes by the create operation, though it does not add any operational scope or parameter context.

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 when-to-use guidance, alternative tools, prerequisites, or exclusions are provided. An agent must infer from the schema and sibling names that this tool is for adding a node, while tools like update_td_node_parameters and exec_node_method exist for other operations. The description gives zero usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools