Skip to main content
Glama
bbernstein

LacyLights MCP Server

by bbernstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

update_cue

Modify an existing lighting cue's name, number, look, notes, skip status, fade-in, fade-out, or follow time to keep playback accurate and organized.

Instructions

Update properties of an existing cue

Input Schema

NameRequiredDescriptionDefault
nameNoNew name for the cue
skipNoWhen true, this cue is skipped during playback but remains visible in the UI
cueIdYesID of the cue to update
notesNoNew notes or description
lookIdNoNew look ID
cueNumberNoNew cue number
fadeInTimeNoNew fade in time in seconds
followTimeNoNew follow time (null to remove auto-follow)
fadeOutTimeNoNew fade out time in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.7.0
    • addedInput schema / properties / lookId
      Added value: +{
+  "description": "New look ID",
+  "type": "string"
+}
    • removedInput schema / properties / sceneId
      Removed value: -{
-  "description": "New scene ID",
-  "type": "string"
-}
    • addedInput schema / properties / skip
      Added value: +{
+  "description": "When true, this cue is skipped during playback but remains visible in the UI",
+  "type": "boolean"
+}
  2. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'Update' implies a mutation, but nothing states whether it requires permissions, whether it is a partial patch (only supplied fields change) or a full replace, whether unmentioned fields are preserved, or whether the change is reversible/undoable given the undo/redo siblings.

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?

A single, front-loaded sentence with zero filler. It is efficient, though arguably too terse given the nine-parameter surface it governs.

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?

A nine-parameter mutation tool with no annotations and no output schema needs more than one sentence. The description omits partial-update behavior, permission/undo implications, and any return-value expectation, leaving key context to inference.

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 nine parameters are already documented in the schema (e.g. skip semantics, followTime null-to-remove). The description adds no additional meaning beyond 'properties of an existing cue', so the baseline 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?

States a clear verb ('Update') and resource ('properties of an existing cue'), and the required cueId implies targeting an existing entity. However, it does not distinguish itself from sibling tools like bulk_update_cues, toggle_cue_skip, or update_cue_list, leaving the agent to infer the scope is a single cue.

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 versus bulk_update_cues (for multiple cues) or the single-property shortcut toggle_cue_skip. No prerequisites, no mention of partial vs full update semantics, and no exclusions are provided.

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