Skip to main content
Glama

Set up body tracking

setup_body_tracking

Sets up real-time body tracking from a webcam in TouchDesigner: loads the MediaPipe engine, runs the timeline, and outputs a 33-landmark pose CHOP with an optional visual skeleton.

Instructions

One-shot body tracking from a webcam: loads the free mediapipe-touchdesigner ENGINE (install it first with tdmcp install mediapipe-touchdesigner) into your project, starts the timeline (the engine captures the webcam through an embedded browser that only runs while playing), reads its pose JSON DAT through an adapter that emits a 33-landmark pose CHOP, and builds a live skeleton so you only need to pick your webcam and enable Pose. If the engine isn't installed yet, it tells you how. Loading the engine will prompt for camera permission on macOS (click Allow).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tox_pathNoPath to the MediaPipe ENGINE .tox (MediaPipe.tox — the full tracker that captures the webcam, not the bare pose_tracking.tox processor). Defaults to the package staged by `tdmcp install mediapipe-touchdesigner`, falling back to the legacy ~/tdmcp-packages path.
parent_pathNoCOMP to load the engine into./project1
build_skeletonNoAlso build a pose-skeleton visual wired to the tracked body so you see it working.
Behavior5/5

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

Beyond the annotations (readOnlyHint false, openWorldHint true, destructiveHint false), the description reveals important behavioral traits: the engine only captures the webcam while playing, it reads pose JSON DAT through an adapter, and macOS shows a camera permission prompt. These are useful disclosures not present in the structured metadata.

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 compact yet information-dense, with a clear logical flow: one-shot setup, installation prerequisite, engine behavior, adapter pipeline, skeleton output, and permission warning. Every sentence contributes new information, and the structure is front-loaded with the core purpose.

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 the tool's moderate complexity, no output schema, and rich annotations, the description covers the complete workflow, prerequisites, runtime behavior, and expected user actions. It even addresses the failure case (engine not installed) and platform-specific permission prompts, making it fully self-contained.

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 baseline is 3. The description adds contextual meaning by explaining the engine (.tox) referenced in tox_path and the live skeleton built by build_skeleton, but it does not directly map each parameter. The schema already provides clear descriptions, so no significant additional parameter semantics are added.

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 verb and resource: 'One-shot body tracking from a webcam.' It details the full workflow (loads mediapipe engine, starts timeline, reads pose JSON, builds skeleton), which distinguishes it from sibling tools like setup_face_tracking and setup_hand_tracking.

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 on when to use this tool (for one-shot body tracking) and includes a prerequisite instruction ('install it first with tdmcp install mediapipe-touchdesigner'). It does not explicitly mention alternatives or exclusions, but the unique webcam body-tracking workflow makes its usage scope evident.

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/lucasmaher-hash/touch-designer-mcp'

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