Skip to main content
Glama

Create LED pixel-mapper

create_led_mapper

Map images from a TOP to LED fixtures over Art-Net or sACN, creating a resizable pixel-mapping network with DMX output and a built-in test source.

Instructions

Build a pixel-mapping chain from a source TOP to an LED fixture grid and DMX Out CHOP over Art-Net or sACN. The generated network resizes to width×height, samples one texel per fixture pixel, preserves RGB channels, and returns created node paths, channel count, warnings, and live Brightness/Universe controls on the parent COMP. It defaults to a moving Ramp test source so the chain can cook without input; real network output still requires a reachable fixture/node and should be verified before sending. Use create_dmx_fixture_pipeline for fixture patching and this tool when you specifically need image-to-pixel mapping.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoOutput frame rate (DMX Out CHOP sample rate).
netNoNetwork DMX protocol: Art-Net or sACN (streaming ACN).artnet
nameNoBase name for the created nodes.
widthNoPixels per row (columns). Each texel of the WxH grid drives one LED fixture.
heightNoRows of pixels. 1 = a single LED strip.
layoutNoPixel wiring order along the strip/grid: horizontal (rows left-to-right), vertical (columns), or serpentine (alternate rows reversed — boustrophedon strips).horizontal
sourceNoTOP path whose image is mapped to the fixtures. If omitted, a built-in moving Ramp TOP test source is created so the chain cooks with no input.
net_addressNoTarget IP address for Art-Net / sACN. Defaults to the operator's own default.
parent_pathNoCOMP to build the pixel-map chain in./project1
start_channelNoDMX start channel (1-512) of the first pixel within the starting universe.
start_universeNoArt-Net / sACN universe of the first pixel.
Behavior4/5

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

Annotations provide readOnlyHint=false, openWorldHint=true, destructiveHint=false. Description adds meaningful behavior: chain resizes, samples texels, preserves RGB, returns node paths/channel count/warnings, defaults to a moving Ramp test source, and warns that real output requires verification. Would benefit from more on potential overwriting of existing nodes, but strong beyond annotations.

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?

Three sentences each earn their place: function, behavior/return values, default/caveat/alternative. Slightly dense but well-structured and front-loaded with the primary purpose.

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?

No output schema, but description compensates by enumerating return values (node paths, channel count, warnings, live controls) and the test source default. Covers prerequisites implicitly with the reachable fixture warning. Complete for a complex tool, though no mention of name collision behavior.

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 all 11 parameters are documented in the schema. The description adds context about width×height resizing and source default, but these are largely already in the schema descriptions. Baseline 3 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?

Specific verb 'Build' + resource 'pixel-mapping chain from source TOP to LED fixture grid and DMX Out CHOP over Art-Net or sACN'. Distinctive from sibling create_dmx_fixture_pipeline, which is explicitly named as an alternative.

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?

Explicitly states 'Use create_dmx_fixture_pipeline for fixture patching and this tool when you specifically need image-to-pixel mapping.' Provides clear when-to-use and alternative tool 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