Skip to main content
Glama

Create object/person detection → parameters

create_detection_reactive

Set up object detection control channels in TouchDesigner using a WebSocket detector or CPU ONNX model, outputting presence, count, and bounding boxes as CHOP channels.

Instructions

Turn object/person detection into TouchDesigner control channels — with NO CUDA requirement. Two backends: 'websocket' subscribes to an external detector process that streams JSON detections over a WebSocket (runs on any machine/GPU, or none), and 'onnx' scaffolds a CPU Script CHOP that runs an .onnx model via onnxruntime inside TD. Either way the output is a Null CHOP carrying a stable contract — presence (0/1), count, and per-object normalized bboxes (obj1_x, obj1_y, obj1_w, obj1_h, obj1_score, …) — ready for bind_to_channel. (Detection idea inspired by TDYolo, MIT-licensed; no code copied.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNo(websocket) URL of the external detector's WebSocket. It should send JSON objects like {"count": N, "objects": [{"x":..,"y":..,"w":..,"h":..,"score":..}]}.ws://127.0.0.1:8765
nameNoBase name for the container COMP.detection
sourceNoDetector backend. 'websocket' subscribes to an external detector process that streams JSON detections (no CUDA needed, runs anywhere). 'onnx' scaffolds a Script CHOP that runs an ONNX model via onnxruntime on the CPU inside TouchDesigner — you fill in the model path + inference.websocket
input_topNo(onnx) Absolute path of the TOP to read frames from for inference. Pulled via a Select TOP.
model_pathNo(onnx) Filesystem path to the .onnx model to load in the Script CHOP (CPU inference).
max_objectsNoNumber of detected objects (bboxes) to expose as channels (obj1_x, obj1_y, …).
parent_pathNoCOMP to create the detection container in (default '/project1')./project1
reconnect_secondsNo(websocket) Auto-reconnect interval if the detector connection drops.
Behavior4/5

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

The description adds behavioral traits beyond annotations: 'no CUDA requirement,' auto-reconnect interval for websocket, and the output contract (presence, count, bboxes). Annotations only provide readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the description fills in important details.

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 three sentences, well-structured, and front-loaded with the main purpose. It includes a parenthetical note about inspiration but no wasted words.

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?

Given 8 parameters, two backends, and no output schema, the description is complete. It explains the output format, backend differences, and key constraints (no CUDA, auto-reconnect).

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 baseline is 3. The description adds minimal extra meaning beyond the schema, summarizing the output structure and backend choice but not providing new parameter-specific details.

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 clearly states the tool's purpose: 'Turn object/person detection into TouchDesigner control channels — with NO CUDA requirement.' It distinguishes between two backends and describes the output format, making it unambiguous. The title 'Create object/person detection → parameters' reinforces this.

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 explains when to use each backend: 'websocket' for external detectors, 'onnx' for CPU inference. It implies context but does not explicitly exclude alternatives or mention when not to use this tool compared to sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server