Skip to main content
Glama

Create interactive projection mapping

create_interactive_projection_mapping

Create an interactive projection mapping rig that turns webcam or synthetic input into projected visuals using motion tracking, blob masks, and corner pin mapping with live controls.

Instructions

Build a synthetic-safe interactive projection mapping rig for a USB webcam plus projector: camera/synthetic/existing TOP input, frame-difference motion field, placeholder blob/post-it mask, cyan dot and magenta card visual TOPs, manual Corner Pin projection mapping, debug switch, live controls, and an out1 Null TOP. Defaults to source='camera' for installations, but source='synthetic' previews without camera permission. Returns output/debug paths and explicit warnings for camera, blob tracking, and physical calibration states.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName for the generated interactive projection mapping Base COMP.interactive_projection_mapping
sourceNoInput source: a USB camera, a self-animated synthetic TOP, or an existing TOP pulled through a Select TOP.camera
dot_colorNoCyan dot color as #rrggbb.#8ff4f2
max_blobsNoMaximum blob slots reserved for the later marker-tracking branch.
card_colorNoMagenta card color as #rrggbb.#ff2f9a
card_countNoTarget count for magenta card blocks. This MVP uses it as visual density metadata.
debug_viewNoWhich branch the debug switch shows initially.final
parent_pathNoParent COMP where the interactive projection mapping system is created./project1
trail_decayNoFeedback persistence for visual trails.
camera_indexNoUSB/webcam device index used when source='camera'.
output_widthNoProjection output width in pixels.
repel_radiusNoNormalized radius metadata for hand/motion repulsion.
output_heightNoProjection output height in pixels.
blob_thresholdNoThreshold used by the placeholder blob/post-it mask branch.
particle_countNoTarget count for the cyan dot field. This MVP uses it as visual density metadata.
expose_controlsNoExpose live controls for calibration/debug/performance tuning.
background_colorNoDark projected background color as #rrggbb.#05100e
interaction_modeNoInteraction branch to prioritize. The first slice always keeps motion available.hybrid
existing_top_pathNoAbsolute TOP path required when source='existing_top'.
motion_sensitivityNoGain over the frame-difference motion field.
analysis_resolutionNoSquare working resolution for cheap motion/blob analysis.
fallback_to_syntheticNoIf camera creation fails, build a synthetic source so the rig remains previewable.
projection_brightnessNoFinal Level TOP brightness before out1.
Behavior4/5

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

Annotations already indicate a mutating, non-destructive, open-world operation. Description adds specifics: 'synthetic-safe', default source behavior, and returns 'explicit warnings for camera, blob tracking, and physical calibration states' — useful behavioral context not present in annotations.

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?

Three sentences, front-loaded purpose, zero filler. Lists key components and behavioral notes efficiently.

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?

Complex 23-parameter tool with no output schema; description informs about return paths and warnings, plus source-mode decision. Slight gap: no explicit guidance on interpreting warnings or when to use existing_top, but schema and description together are sufficient.

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 covers 100% of parameters with descriptions. Description adds high-level context (defaults, warnings) but does not detail individual parameter syntax beyond what schema provides.

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?

Description opens with a specific verb 'Build' and resource 'interactive projection mapping rig for a USB webcam plus projector', enumerating components. This clearly differentiates from siblings like create_projection_mapping by emphasizing interactivity and webcam/synthetic source.

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?

Provides context on source default and synthetic preview, but does not explicitly name when to use this vs alternatives like create_projection_mapping or projector_calibration_wizard. Exclusion criteria are absent.

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