Skip to main content
Glama
Sign In
bbernstein

LacyLights MCP Server

by bbernstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_cue_to_list

Add a new cue to an existing cue list by setting its name, cue number, look, fade times, and optional insertion point. Use it to insert lighting cues before or after a reference cue.

Instructions

Add a new cue to an existing cue list

Input Schema

NameRequiredDescriptionDefault
nameYesName for the new cue
notesNoNotes or description for the cue
lookIdYesLook ID to use for this cue
positionNoPosition relative to reference cue
cueListIdYesCue list ID to add cue to
cueNumberYesCue number (e.g., 1.5, 2.0)
fadeInTimeNoFade in time in seconds
followTimeNoAuto-follow time in seconds (null for manual)
fadeOutTimeNoFade out time in seconds
referenceCueNumberNoCue number to insert before/after

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • addedInput schema / properties / lookId
      Added value: +{
+  "description": "Look ID to use for this cue",
+  "type": "string"
+}
    • removedInput schema / properties / sceneId
      Removed value: -{
-  "description": "Scene ID to use for this cue",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "cueListId",
-  "name",
-  "cueNumber",
-  "sceneId"
-]New value: +[
+  "cueListId",
+  "name",
+  "cueNumber",
+  "lookId"
+]
  2. First observedv1.0.0

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description bears full behavioral burden and delivers almost none. It does not disclose whether inserting a cue renumbers/shifts existing cues, how position/referenceCueNumber interact with the required fields, permission requirements, or reversibility of the mutation.

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?

It is a single front-loaded sentence with no filler, which is good. But the extreme brevity leaves the definition under-specified for a 10-parameter mutation tool, so it is concise without being appropriately sized.

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

Completeness2/5

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

For a 10-parameter write operation with no annotations and no output schema, the description is inadequate. Nothing explains the insertion semantics, the interaction between position, referenceCueNumber, and cueNumber, or what the caller should expect afterward.

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 10 parameters (including the before/after enum and the fade timings) are already documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource ('Add a new cue to an existing cue list'), which is enough to distinguish it from siblings like remove_cue_from_list. However, it never explicitly contrasts itself with alternatives such as bulk_create_cues, create_cue_sequence, or update_cue, so the differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus bulk_create_cues, create_cue_sequence, or update_cue, and no stated preconditions (e.g., that the cue list must already exist). The 'existing cue list' phrasing faintly implies a prerequisite but nothing actionable is offered.

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