tdmcp

Create pointer reactive

create_pointer_reactive

Builds a TouchDesigner CHOP network that converts mouse position and clicks into normalized pointer channels (u, v, velocity, button) with optional visual feedback demo.

Instructions

Turn mouse/pointer position and click into a first-class creative seed. Builds a Mouse In CHOP → normalized u/v (0..1) + velocity (vu/vv) + button, exposed on a 'pointer' Null CHOP ready for binding: op('…/pointer_reactive/pointer')['u'] / ['v'] / ['button'] / ['vu'] / ['vv']. A Sensitivity knob gains every channel. By default also builds a small visible demo — a bright dot that follows the pointer and leaves a decaying trail over a feedback field — so you immediately see it working; set demo=false to build only the CHOP chain (no image, no preview). multitouch is reserved for a future Panel-COMP touch source; this build always uses Mouse In and reports the limitation as a warning when requested. Creates a new baseCOMP under parent_path. Returns a summary plus a JSON block with the container path, created node paths, the pointer Null path, channel names, exposed controls, any node errors, and warnings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_pointer_reactive"
  }
}

Input Schema

Name	Required	Description	Default
`demo`	No	Also build a visible feedback-field demo the pointer pushes, so you see it working immediately (a bright dot that trails behind the mouse over a decaying feedback field).
`multitouch`	No	When true, note that true multitouch needs a Panel COMP touch source; this build always uses Mouse In (single pointer) and reports the limitation as a warning. Kept for forward-compat — it does not change what gets built.
`resolution`	No	Output resolution [width, height] in pixels for the demo feedback field.
`parent_path`	No	Parent network where the pointer-reactive container is created (default '/project1').	/project1
`sensitivity`	No	Gain applied to every pointer channel (u, v, velocity, button) before the output.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A4.4/5.0

Behavior5/5

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

The description fully discloses side effects beyond the annotations: it 'Creates a new baseCOMP under parent_path', builds a demo by default, and reports node errors and warnings. It also states the return format ('a summary plus a JSON block with the container path, created node paths...'). This goes well beyond the basic readOnly/destructive hints and describes exactly what the agent can expect.

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 long but every sentence carries meaningful info: purpose, node structure, channel names, demo behavior, multitouch limitation, creation path, and return value. It front-loads the core purpose and organizes details logically. A slight structural improvement would be splitting into paragraphs, but it's dense and not wasteful.

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

Completeness5/5

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

For a tool with no output schema and 5 parameters, the description is remarkably complete: it explains what is built, how to access channels (including exact paths), the demo variant, the multitouch caveat, and the return value (summary + JSON with paths, channels, controls, errors, warnings). This covers all the information an agent needs to invoke and understand the result, and even includes edge-case warnings.

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%, and each parameter (demo, multitouch, resolution, parent_path, sensitivity) has a clear description with defaults. The tool description adds only marginal references (e.g., 'Sensitivity knob gains every channel'), which is already in the schema. With full schema coverage, a baseline of 3 is appropriate; the description doesn't need to compensate.

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 opens with a clear, specific verb+resource statement ('Turn mouse/pointer position and click into a first-class creative seed') and then details exactly what is built: a Mouse In CHOP → normalized u/v + velocity + button on a 'pointer' Null CHOP. This distinguishes it from sibling tools like create_motion_reactive or create_audio_reactive by focusing on pointer input.

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 makes clear when to use the tool (for pointer/mouse reactive builds) and gives practical guidance on the demo flag ('set demo=false to build only the CHOP chain'). It also notes the multitouch limitation and that the build always uses Mouse In, effectively telling the agent that this tool is for single-pointer/mouse scenarios. However, it does not explicitly name alternatives or say 'use this instead of X', so it doesn't fully meet the 'when-not-to' bar.

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

Deploy Server