Skip to main content
Glama

Create moving-head fixture control + 3D previz

create_fixture_control

Build a moving-head lighting rig with DMX/Art-Net output and real-time 3D previsualization. Each fixture gets a constant channel block and a geometry head with rotating beam, enabling live preview alongside DMX control.

Instructions

Build a moving-head lighting rig with BOTH a DMX/Art-Net output chain AND a 3D visual previsualization. For each fixture: a Constant CHOP holds an 8-channel movingHead8 block (pan, tilt, dimmer, r, g, b, strobe, gobo, prefixed '/…'), padded and merged into a dmxoutCHOP (interface, universe, netaddress, rate); and a Geometry COMP 'head' with a tube-cone beam whose pan→ry and tilt→rx rotation is expression-driven straight from that fixture's DMX pan/tilt channels (0-255 mapped across pan_range/tilt_range degrees), all rendered under one camera+light Render TOP. This adds the live 3D preview on top of what create_dmx_fixture_pipeline (DMX-out only) does. Bind individual channels later with bind_to_channel / animate_parameter on op('rig_out')['fix1/pan']; the previz updates automatically.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoDMX refresh rate (dmxoutCHOP `rate`).
netNoNetwork protocol — written to the dmxoutCHOP `interface` par.artnet
hostNoTarget IP for Art-Net / sACN (dmxoutCHOP `netaddress`). Null = leave default.
nameNoBase name for the container COMP.fixture_rig
fixturesYesMoving-head fixtures. Each becomes a DMX movingHead8 block + a 3D previz head+beam.
universeNoDMX universe written to the dmxoutCHOP.
pan_rangeNoPhysical pan sweep in degrees the fixture spans across DMX 0-255 (previz rotation).
beam_angleNoHalf-angle of the previz beam cone (degrees) — narrow = spot, wide = wash.
tilt_rangeNoPhysical tilt sweep in degrees the fixture spans across DMX 0-255 (previz rotation).
beam_lengthNoLength of the previz beam cone from the head (metres).
parent_pathNoCOMP to create the fixture rig container in (default '/project1')./project1
Behavior3/5

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

Description details what components are created (CHOP, Geometry COMP, etc.) and the automatic previz updates. Annotations already indicate non-readOnly and openWorld. Could be more explicit about side effects like overwriting, but no contradiction.

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 long but front-loads core purpose and is well-structured with technical details, sibling comparison, and usage example. Some jargon density, but each sentence adds value.

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 provides a thorough walkthrough of the internal construction and behavior. It explains the previz mechanics and gives a binding example. Could mention what is returned or created, but overall complete for its complexity.

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%, so baseline 3. Description adds meaning by linking parameters like pan_range/tilt_range to expression mapping and mentioning dmxoutCHOP parameters (interface, universe, netaddress, rate) which correspond to net, universe, host, fps.

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 explicitly states it builds a moving-head rig with both DMX/Art-Net output and 3D previz. It clearly distinguishes from sibling create_dmx_fixture_pipeline (DMX-only). Verb and resource are specific.

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?

Explicitly mentions the added 3D preview over the sibling tool, providing a clear when-to-use criterion. Also gives an example of later binding channels, but lacks explicit when-not-to-use or prerequisites.

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