Skip to main content
Glama
Sign In
TouchDesigner MCP

TouchDesigner MCP

by 8beeeaaat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

execute_python_script

Run Python scripts in TouchDesigner to create, modify, or query nodes and project structures. Choose detail level and response format for structured output.

Instructions

Execute a Python script in TouchDesigner (detailLevel=minimal|summary|detailed, responseFormat=json|yaml|markdown)

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": {
      "script": "<script>"
    },
    "name": "execute_python_script"
  }
}

Input Schema

NameRequiredDescriptionDefault
scriptYese.g., "op('/project1/text_over_image').outputConnectors[0].connect(op('/project1/out1'))"
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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Execute a Python script' and lists output formatting options, but it does not warn about potential side effects (e.g., modifying the TouchDesigner environment, executing arbitrary code), require any permissions, or explain error handling. The description adds minimal behavioral context beyond what the name implies.

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, efficient sentence that states the core action and lists the two optional parameters inline. It is front-loaded with the purpose and avoids unnecessary verbosity. It earns a 4 because it is concise, though the parenthetical parameter listing is somewhat redundant with the schema.

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?

Given that this tool executes arbitrary Python code, the description is incomplete. It does not explain the execution environment (e.g., how to reference TouchDesigner objects), potential side effects, error handling, or what the script is expected to return. The output format options are mentioned, but the description lacks essential context for an agent to use the tool safely and effectively.

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 schema description coverage is 100%, so the baseline is 3. The description repeats the enum values for detailLevel and responseFormat but adds no additional meaning beyond what the schema already provides. It doesn't clarify the semantics of the 'script' parameter beyond the example, which is already in the schema. Thus, no extra value is added.

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 a specific verb ('Execute') and resource ('Python script in TouchDesigner'), which distinguishes it from the sibling tools that are mostly about querying or modifying nodes. However, it doesn't explicitly differentiate itself from siblings like exec_node_method or update_td_node_parameters, so it loses a point for not naming alternatives. Overall, the purpose is unambiguous and specific.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to prefer it over update_td_node_parameters, exec_node_method, or any other sibling. There are no conditions, exclusions, or recommendations, leaving the agent without direction on selection.

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