Skip to main content
Glama
bbernstein

LacyLights MCP Server

by bbernstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

import_eos_ascii

Import an ETC Eos ASCII (.asc) showfile into LacyLights, creating or appending a project with patch, cues, palettes, and groups while warning about skipped EOS-only data.

Instructions

Import an ETC Eos ASCII (.asc) showfile into LacyLights.

Creates a new project (or appends into an existing one if targetProjectId is given) populated with the patch, cues, palettes, and groups from the Eos showfile. EOS-only concepts (effects, partitions, magic sheets, action triggers, curves, submasters) are skipped and surfaced as structured warnings. Palettes/presets are imported as standalone Looks in dedicated cue lists ("Color Palettes", "Beam Palettes", etc.).

Returns:

  • projectId: the created or updated project

  • counts of fixtures, looks, cue lists, cues, groups created

  • warnings: structured list with code/severity/message/context entries

  • synthesizedDefinitionIds: definitions auto-synthesized when no library match was found

Provide either newProjectName or targetProjectId, not both. If both are omitted, the project name comes from the showfile's $$Title.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
asciiContentYesFull text content of the .asc showfile.
newProjectNameNoOptional explicit name for the new project.
targetProjectIdNoOptional existing project ID to append the import into. Existing data is preserved.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so richly: it discloses what is imported (patch, cues, palettes, groups), what is silently skipped and surfaced as warnings (effects, partitions, magic sheets, etc.), how palettes are remapped into Looks, and the structured return payload. This is well beyond what structured fields provide.

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?

Front-loads purpose, then behavior, then return shape, then parameter constraints. The Returns list is justified because no output schema exists, and no sentence is redundant.

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

Completeness5/5

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

For a complex import tool with no output schema, the description covers side effects, skipped content, warning structure, synthesized definitions, and parameter rules. An agent has everything needed to call it correctly.

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 the baseline is 3, but the description adds real meaning: newProjectName and targetProjectId are mutually exclusive, and if both are omitted the name is derived from the showfile's $$Title. That constraint is not visible in the schema.

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?

States a specific verb and resource: 'Import an ETC Eos ASCII (.asc) showfile into LacyLights.' It also names the sibling it is the inverse of (export_eos_ascii is in the sibling list), so an agent can distinguish import from export immediately.

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?

Gives clear context: creates a new project, or appends into an existing one when targetProjectId is supplied. It does not name alternatives or state when NOT to use it, but the usage conditions for its two modes are explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools