Skip to main content
Glama

Set up MediaPipe plugin (multi-modal)

setup_mediapipe_plugin

Loads the MediaPipe engine once to enable face, hand, body, or segmentation pipelines, preventing multiple competing webcam instances.

Instructions

Drop the torinmb mediapipe-touchdesigner ENGINE in one shot and enable any combination of face, hand, body, and segmentation pipelines. Use this instead of running setup_face_tracking + setup_hand_tracking + setup_body_tracking + setup_segmentation separately — those tools each re-load the engine, resulting in multiple competing MediaPipe COMPs fighting for the webcam. This tool loads the engine ONCE and toggles its Face/Hand/Body/Segmentation pars. IMPORTANT: there is NO stock TouchDesigner MediaPipe; all five mediapipe tools (this one + the four setup_*_tracking tools) rely on the free torinmb plugin — install it first with tdmcp install mediapipe-touchdesigner. Output paths for face/hand/body are DATs (JSON landmark streams from the plugin), not CHOPs — use a Script CHOP adapter to convert to numeric channels. The engine requires the TD timeline to be PLAYING (uses an embedded browser for webcam capture).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tox_pathNoOverride path to the torinmb mediapipe-touchdesigner ENGINE .tox (MediaPipe.tox — the full tracker with webcam capture, NOT the bare pose_tracking.tox or hand_tracking.tox processors). Defaults to the package staged by `tdmcp install mediapipe-touchdesigner`.
enable_bodyNoEnable the Body/Pose tracking pipeline inside the engine.
enable_faceNoEnable the Face detection pipeline inside the engine.
enable_handNoEnable the Hand tracking pipeline inside the engine.
parent_pathNoExisting COMP to load the engine into./project1
container_nameNoInner baseCOMP name. Matches the default used by setup_body_tracking / setup_hand_tracking so re-running is idempotent (the engine is reused, not duplicated).MediaPipe
source_video_pathNoOptional path to a video file to use as input instead of the live webcam. The engine's Camera/Source/Videofile/File par is probed in that order and the first match is set.
enable_segmentationNoEnable the Segmentation pipeline (outputs a matte TOP; heavier GPU cost than the landmark pipelines).
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 crucial behavioral details: the tool loads the engine once, toggles pars, requires the timeline to be playing (embedded browser webcam), and outputs DATs rather than CHOPs. It also warns that there is no stock MediaPipe and all five tools rely on the torinmb plugin.

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 dense but every sentence serves a purpose: purpose, differentiation, prerequisite, behavioral quirks, and output format. It is front-loaded with the primary action and maintains a logical flow without repeating parameter schema details. No fluff.

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 complex setup tool with 8 parameters, no output schema, and multiple sibling tools, the description covers prerequisites, alternatives, side effects, output types, and operational constraints (timeline playing, container_name idempotency). It is thorough enough for an agent to safely invoke the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter already well-described. The tool description adds value beyond the schema by explaining that enabling pipelines produces DAT outputs and describing the source_video_path probing order, which is not fully captured in parameter descriptions. This enriches parameter understanding, so a slight upgrade from baseline is warranted.

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+resource ('Drop the torinmb mediapipe-touchdesigner ENGINE') and clearly states the tool's scope (enable any combination of face, hand, body, and segmentation pipelines). It also distinguishes itself from the four setup_*_tracking siblings, which is a key differentiator.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly tells the agent to use this tool instead of running the four separate setup tools, explaining why (each reloads the engine, causing competing MediaPipe COMPs). It also names the prerequisite install step ('tdmcp install mediapipe-touchdesigner') and notes the timeline playing requirement, providing complete usage guidance.

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