tdmcp

Create companion surface

create_companion_surface

Automatically create a companion control surface for a TouchDesigner node: infer usable parameters, bind custom controls, and add faders, cue buttons, and a preflight report.

Instructions

Build a companion performance surface for an existing node/COMP: infer useful primitive parameters, add bound custom parameters, create a playable fader/cue panel, and optionally append a read-only preflight report. Use after generating a component that needs a human-facing control surface without hand-wiring every parameter.

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": {
      "source_path": "<source_path>"
    },
    "name": "create_companion_surface"
  }
}

Input Schema

Name	Required	Description	Default
`bind`	No	Bind generated custom parameters back to source_path parameters.
`name`	No	Name of the playable panel container to build.	companion_surface
`page`	No	Custom-parameter page added by the auto UI pass.	Companion
`exclude`	No	Source parameter names to skip.
`comp_path`	No	COMP that receives the custom parameters and panel. Defaults to source_path.
`parameters`	No	Only expose these source parameter names. Omit to infer primitive controls.
`target_fps`	No	Frame-rate target for preflight.
`cue_buttons`	No	Optional cue buttons to add to the playable surface.
`source_path`	Yes	Node or COMP whose useful parameters should be surfaced.
`max_controls`	No	Maximum inferred controls when parameters is omitted.
`include_faders`	No	Build a playable fader/toggle surface for numeric inferred controls.
`include_preflight`	No	Append a read-only show_preflight_report result for the companion COMP.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, setting the safety profile. The description adds valuable behavioral context by specifying that it will infer primitive controls, bind custom parameters, create a playable panel, and optionally append a read-only preflight report. No contradiction with annotations.

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 two sentences: the first packs the entire pipeline into a clear action list, and the second defines the exact use case. Every word earns its place; no fluff or redundancy.

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

Completeness4/5

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

For a 12-parameter builder tool with no output schema, the description adequately frames the workflow and purpose. The rich schema covers parameters, and the description supplies the missing context around 'companion surface' and when to use it. It does not explain return values or error cases, but these are not required given the lack of output schema.

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%, so the baseline is 3. The description adds high-level context about why parameters exist (inference, binding, hiding/limiting) but does not add syntax or format details beyond what the schema already provides.

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 and resource: 'Build a companion performance surface for an existing node/COMP' and enumerates concrete sub-actions (infer parameters, add bound custom parameters, create fader/cue panel, optionally append preflight report). This clearly distinguishes it from sibling tools like 'connect_companion_surface' and 'create_control_surface'.

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 provides clear context: 'Use after generating a component that needs a human-facing control surface without hand-wiring every parameter.' It indicates when to use the tool but does not mention when not to use it or name specific alternatives, so it falls short of a 5.

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

Deploy Server