Skip to main content
Glama
Sign In
TouchDesigner MCP

TouchDesigner MCP

by 8beeeaaat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_td_node

Delete a TouchDesigner node by providing its path, removing unwanted elements from the project structure.

Instructions

Delete an existing 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": {
      "nodePath": "<nodePath>"
    },
    "name": "delete_td_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodePathYesPath to the node to delete. e.g., "/project1/geo1"
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

B3.2/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral disclosure burden. It states that the tool deletes a node but does not disclose whether the action is irreversible, what happens to connected references/dependencies, whether confirmation is required, or what the result/return value looks like. For a destructive operation this is a significant transparency gap.

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 a single, focused sentence with no filler or redundant explanation. It front-loads the verb and resource and earns its place as a concise definition.

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 destructive tool with no annotations and no output schema, the description is too thin. It does not mention irreversibility, side effects on dependent nodes, error cases, or what output to expect, leaving an agent without enough context to anticipate consequences.

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 description coverage is 100%, so the schema already documents the nodePath parameter and the output formatting parameters. The description adds no parameter-level meaning, but the baseline of 3 applies because the schema does the required work.

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 uses a specific verb ('Delete') and a clear resource ('an existing node in TouchDesigner'). It stands apart from sibling tools like create_td_node and update_td_node_parameters, making the tool's role immediately obvious.

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?

There is no guidance about when to use this tool versus alternatives, nor any mention of prerequisites or conditions. The intended use is only implied by the verb 'delete' and the resource name.

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