Skip to main content
Glama

Create LED pixel-mapper

create_led_mapper

Map a source image onto an LED fixture layout and output per-pixel colors as DMX over Art-Net or sACN. Resizes the image to a grid of fixture pixels, samples color channels, and feeds into a DMX output chain.

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?

Beyond annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description adds behavioral context: it creates nodes in a COMP, defaults to a test source, and exposes controls. No contradiction with 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?

Description is dense but clear, front-loading the main action. Every sentence adds information, though could be slightly more concise. No wasted words.

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?

Given 11 parameters and no output schema, the description is quite complete. It explains the core process, defaults, and networking requirement. Missing explicit mention of return values, but that's acceptable without output schema.

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%, baseline 3. Description adds value by explaining parameter purposes beyond schema, e.g., source defaults, layout wiring order, and test source behavior. Not all parameters get extra context, but enough to earn a 4.

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 clearly states the tool's purpose: pixel-map a source TOP onto LED fixtures and output DMX. It provides specific details about the process and distinguishes itself from sibling tools (unique functionality).

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

Usage Guidelines4/5

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

Description indicates when to use the tool (for LED mapping and DMX output) and mentions a prerequisite (need a fixture/node for real Art-Net). It doesn't explicitly state when not to use or provide alternatives, which prevents a higher score.

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