Skip to main content
Glama

Create LED pixel-mapper

create_led_mapper

Map a source image to a grid of LED fixtures and output pixel colors as Art-Net or sACN DMX. Automatically builds the TouchDesigner network with a built-in test source.

Instructions

Pixel-map a source TOP onto an LED fixture layout and send per-pixel colors out as DMX over Art-Net/sACN. Resizes the source to a tiny WxH grid (one texel = one fixture pixel), samples it into per-pixel r/g/b channels with a TOP-to-CHOP, and feeds those into a DMX Out CHOP — the pixel-mapping editor that artnet_out lacked. Defaults to a built-in moving test source so the chain cooks with no input. Exposes Brightness and Universe controls. Sending real Art-Net needs a fixture/node on the network; this validates the per-pixel color CHOP is correct.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
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
start_universeNoArt-Net / sACN universe of the first pixel.
start_channelNoDMX start channel (1-512) of the first pixel within the starting universe.
netNoNetwork DMX protocol: Art-Net or sACN (streaming ACN).artnet
net_addressNoTarget IP address for Art-Net / sACN. Defaults to the operator's own default.
fpsNoOutput frame rate (DMX Out CHOP sample rate).
parent_pathNoCOMP to build the pixel-map chain in./project1
nameNoBase name for the created nodes.
Behavior4/5

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

The description discloses the internal chain ('TOP-to-CHOP, DMX Out CHOP'), the default test source behavior, and validation of the color CHOP. This adds context beyond annotations (readOnlyHint=false, destructiveHint=false) without contradiction, though it could further detail error handling or rate limiting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is moderately sized but contains redundancy (e.g., repeating the network fixture requirement) and could be more streamlined without losing key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description adequately covers overall functionality and key details (test source, network requirement) but misses error handling, behavior when parent_path does not exist, and output format, leaving some gaps for a tool with 11 parameters.

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

Parameters2/5

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

While schema coverage is 100% and parameters are documented, the description claims 'Exposes Brightness and Universe controls' but the schema lacks a brightness parameter, creating confusion. The description adds minimal extra semantic value beyond the existing 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 the tool's purpose: 'Pixel-map a source TOP onto an LED fixture layout and send per-pixel colors out as DMX over Art-Net/sACN.' It specifies the verb (pixel-map), resource (source TOP), and outcome (send DMX), distinguishing it from sibling tools like create_dmx_fixture_pipeline by emphasizing the pixel-mapping process.

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 implies use for LED pixel mapping but lacks explicit guidance on when to use this tool over alternatives such as create_dmx_fixture_pipeline. It mentions a prerequisite ('sending real Art-Net needs a fixture/node on the network') but no when-not-to-use or explicit exclusions.

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