Skip to main content
Glama
bbernstein

LacyLights MCP Server

by bbernstein

update_cue

Modify properties of a theatrical lighting cue, including name, scene ID, fade timings, and notes, ensuring precise adjustments for LacyLights MCP Server's lighting design.

Instructions

Update properties of an existing cue

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cueIdYesID of the cue to update
cueNumberNoNew cue number
fadeInTimeNoNew fade in time in seconds
fadeOutTimeNoNew fade out time in seconds
followTimeNoNew follow time (null to remove auto-follow)
nameNoNew name for the cue
notesNoNew notes or description
sceneIdNoNew scene ID

Implementation Reference

  • The main execution handler for the 'update_cue' tool. Parses arguments, calls the GraphQL client to update the cue, formats the response with success indicator and cue details.
    async updateCue(args: {
      cueId: string;
      name?: string;
      cueNumber?: number;
      sceneId?: string;
      fadeInTime?: number;
      fadeOutTime?: number;
      followTime?: number | null;
      notes?: string;
    }) {
      const { cueId, ...updateFields } = args;
    
      try {
        const updatedCue = await this.graphqlClient.updateCue(
          cueId,
          updateFields,
        );
    
        return {
          cueId: updatedCue.id,
          cue: {
            name: updatedCue.name,
            cueNumber: updatedCue.cueNumber,
            sceneName: updatedCue.scene.name,
            fadeInTime: updatedCue.fadeInTime,
            fadeOutTime: updatedCue.fadeOutTime,
            followTime: updatedCue.followTime,
            notes: updatedCue.notes,
          },
          success: true,
        };
      } catch (error) {
        throw new Error(`Failed to update cue: ${error}`);
      }
    }
  • src/index.ts:1402-1442 (registration)
    MCP tool registration including name 'update_cue', description, and input schema definition in the list_tools response.
      name: "update_cue",
      description: "Update properties of an existing cue",
      inputSchema: {
        type: "object",
        properties: {
          cueId: {
            type: "string",
            description: "ID of the cue to update",
          },
          name: {
            type: "string",
            description: "New name for the cue",
          },
          cueNumber: {
            type: "number",
            description: "New cue number",
          },
          sceneId: {
            type: "string",
            description: "New scene ID",
          },
          fadeInTime: {
            type: "number",
            description: "New fade in time in seconds",
          },
          fadeOutTime: {
            type: "number",
            description: "New fade out time in seconds",
          },
          followTime: {
            type: "number",
            description: "New follow time (null to remove auto-follow)",
          },
          notes: {
            type: "string",
            description: "New notes or description",
          },
        },
        required: ["cueId"],
      },
    },
  • src/index.ts:2353-2365 (registration)
    Handler dispatch in the CallToolRequestSchema that routes 'update_cue' calls to cueTools.updateCue method.
    case "update_cue":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await this.cueTools.updateCue(args as any),
              null,
              2,
            ),
          },
        ],
      };
  • GraphQL client helper method that performs the actual cue update mutation via GraphQL.
    async updateCue(id: string, input: {
      name?: string;
      cueNumber?: number;
      sceneId?: string;
      fadeInTime?: number;
      fadeOutTime?: number;
      followTime?: number | null;
      notes?: string;
    }): Promise<Cue> {
      const mutation = `
        mutation UpdateCue($id: ID!, $input: CreateCueInput!) {
          updateCue(id: $id, input: $input) {
            id
            name
            cueNumber
            fadeInTime
            fadeOutTime
            followTime
            notes
            scene {
              id
              name
            }
          }
        }
      `;
    
      // Get current cue to maintain required fields
      const cueQuery = `
        query GetCue($id: ID!) {
          cue(id: $id) {
            id
            name
            cueNumber
            cueList {
              id
            }
            scene {
              id
            }
            fadeInTime
            fadeOutTime
            followTime
            notes
          }
        }
      `;
      
      const cueData = await this.query(cueQuery, { id });
      const currentCue = cueData.cue;
      
      const updateInput = {
        name: input.name ?? currentCue.name,
        cueNumber: input.cueNumber ?? currentCue.cueNumber,
        cueListId: currentCue.cueList.id,
        sceneId: input.sceneId ?? currentCue.scene.id,
        fadeInTime: input.fadeInTime ?? currentCue.fadeInTime,
        fadeOutTime: input.fadeOutTime ?? currentCue.fadeOutTime,
        followTime: input.followTime !== undefined ? input.followTime : currentCue.followTime,
        notes: input.notes !== undefined ? input.notes : currentCue.notes
      };
    
      const data = await this.query(mutation, { id, input: updateInput });
      return data.updateCue;
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it updates properties without disclosing behavioral traits. It doesn't mention permissions needed, whether changes are reversible, rate limits, or what happens to unspecified properties (e.g., partial updates). This is inadequate for a mutation tool with zero annotation coverage.

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?

The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It's front-loaded and wastes no space, making it easy for an agent to parse quickly.

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?

Given the complexity of an 8-parameter mutation tool with no annotations and no output schema, the description is insufficient. It lacks details on behavioral aspects, usage context, and return values, leaving significant gaps for an agent to understand the tool's full implications.

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 the schema fully documents all 8 parameters. The description adds no additional meaning beyond implying that properties can be updated, which doesn't enhance the schema's details. This meets the baseline for high schema coverage but doesn't compensate with extra insights.

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 clearly states the action ('Update') and resource ('properties of an existing cue'), making the purpose unambiguous. However, it doesn't differentiate this tool from sibling tools like 'update_cue_list' or 'update_scene', which also modify cue-related entities, so it doesn't reach the highest score.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing cue ID), exclusions, or comparisons to siblings like 'update_cue_list' or 'reorder_cues', leaving the agent with minimal context for selection.

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

Related 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/bbernstein/lacylights-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server