Skip to main content
Glama

Create hand Ableton mapper

create_hand_ableton_mapper

Build a MediaPipe-hands to TDAbleton control network, outputting pinch and wrist roll maps with skeleton overlay, and optionally relink existing TDA_Mapper.

Instructions

Build a MediaPipe-hands to TDAbleton TDA_Mapper performance control network. It outputs map1=left pinch, map2=right pinch, map3=left wrist roll, map4=right wrist roll, creates a skeleton overlay with star joints plus the thumb-index line, and optionally relinks an existing TDA_Mapper to the generated mapper_send CHOP. Uses TDAbleton directly; AbletonMCP is not required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoParent COMP for the mapper network./project1
container_nameNobaseCOMP created under parent_path.hand_ableton_mapper
hand_chopNoExisting hand CHOP with tx/ty/tz/confidence/handedness/screen_x/screen_y. Defaults to setup_hand_tracking's adapter output.
ensure_hand_trackingNoWhen hand_chop is omitted, run setup_hand_tracking first.
tox_pathNoOptional MediaPipe.tox path forwarded to setup_hand_tracking.
adapter_nameNoHand adapter name used by setup_hand_tracking.mp_hand_adapter
coordinate_spaceNoCoordinate space forwarded to setup_hand_tracking; world is best for pinch distance.world
hand_countNoNumber of hand slots.
closed_distanceNoDistance where thumb/index are treated as closed.
open_distanceNoDistance where thumb/index are treated as fully open.
smoothingNo0=raw, 0.99=very slow smoothing.
min_confidenceNoMinimum landmark confidence to accept a hand slot.
invert_pinchNoInvert map1/map2 pinch values.
invert_wristNoInvert map3/map4 wrist-roll values.
fallback_slotsNoIf handedness is missing, treat slot 0 as left and slot 1 as right.
mapper_pathNoOptional explicit TDA_Mapper path.
link_mapperNoTry to set the TDA_Mapper Oscinputchop/Reorder/range parameters.
create_overlayNoCreate a skeleton overlay TOP with star joints and a thumb-index line.
line_widthNoOverlay line width.
star_sizeNoOverlay star-joint size.
Behavior4/5

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

The description adds behavioral context beyond annotations: it creates a network with specific outputs, skeleton overlay, and optional relinking of TDA_Mapper. Annotations indicate non-destructive creation, and the description aligns without contradictions.

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 with clear front-loading of purpose. No unnecessary wording; every sentence provides essential information. Highly efficient.

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?

The description covers key outputs and optional relinking, but for a complex tool with 20 parameters, it omits potential prerequisites (e.g., hand tracking setup) and error handling. However, parameter descriptions fill many gaps, making it sufficiently complete.

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 summarizes outputs but adds no new parameter details. It complements the schema without adding semantic value beyond what is already in parameter descriptions.

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 'Build a MediaPipe-hands to TDAbleton TDA_Mapper performance control network', specifying the tool's exact purpose and outputs (map1-map4, skeleton overlay). It distinguishes this from many other 'create_*' sibling tools by focusing on hand-to-Ableton mapping.

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

Usage Guidelines3/5

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

The description provides context ('Uses TDAbleton directly; AbletonMCP is not required') but does not explicitly state when not to use this tool or list alternatives. It implies usage for hand-to-Ableton control but lacks exclusion criteria.

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