Skip to main content
Glama
bbernstein

LacyLights MCP Server

by bbernstein

get_project_details

Retrieve comprehensive details of a specific project by providing its ID, enabling users to manage and analyze theatrical lighting designs effectively within the LacyLights MCP Server.

Instructions

Get detailed information about a specific project

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject ID to get details for

Implementation Reference

  • Main tool handler: Fetches full project details including fixtures (grouped by universe with channel ranges), scenes summary, and cue lists summary. Organizes and sorts fixture data for easy consumption.
    async getProjectDetails(args: z.infer<typeof GetProjectDetailsSchema>) {
      const { projectId } = GetProjectDetailsSchema.parse(args);
    
      try {
        const project = await this.graphqlClient.getProject(projectId);
    
        if (!project) {
          throw new Error(`Project with ID ${projectId} not found`);
        }
    
        // Organize fixtures by universe
        const fixturesByUniverse = project.fixtures.reduce((acc, fixture) => {
          if (!acc[fixture.universe]) {
            acc[fixture.universe] = [];
          }
          acc[fixture.universe].push(fixture);
          return acc;
        }, {} as Record<number, typeof project.fixtures>);
    
        // Sort fixtures within each universe by start channel
        Object.values(fixturesByUniverse).forEach(fixtures => {
          fixtures.sort((a, b) => a.startChannel - b.startChannel);
        });
    
        return {
          project: {
            id: project.id,
            name: project.name,
            description: project.description,
            createdAt: project.createdAt,
            updatedAt: project.updatedAt
          },
          fixtures: {
            total: project.fixtures.length,
            byUniverse: Object.entries(fixturesByUniverse).map(([universe, fixtures]) => ({
              universe: parseInt(universe),
              fixtureCount: fixtures.length,
              channelRanges: this.calculateChannelRanges(fixtures),
              fixtures: fixtures.map(f => ({
                id: f.id,
                name: f.name,
                type: f.type,
                manufacturer: f.manufacturer,
                model: f.model,
                mode: f.modeName,
                channels: `${f.startChannel}-${f.startChannel + f.channelCount - 1}`,
                tags: f.tags
              }))
            }))
          },
          scenes: {
            total: project.scenes.length,
            list: project.scenes.map(s => ({
              id: s.id,
              name: s.name,
              description: s.description,
              fixtureCount: s.fixtureValues?.length || 0
            }))
          },
          cueLists: {
            total: project.cueLists.length,
            list: project.cueLists.map(cl => ({
              id: cl.id,
              name: cl.name,
              description: cl.description,
              cueCount: cl.cues?.length || 0
            }))
          }
        };
      } catch (error) {
        throw new Error(`Failed to get project details: ${error}`);
      }
    }
  • Zod input validation schema for the getProjectDetails handler.
    const GetProjectDetailsSchema = z.object({
      projectId: z.string().describe('Project ID to get details for')
    });
  • src/index.ts:1832-1844 (registration)
    MCP CallToolRequestHandler switch case that delegates execution to projectTools.getProjectDetails
    case "get_project_details":
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(
              await this.projectTools.getProjectDetails(args as any),
              null,
              2,
            ),
          },
        ],
      };
  • src/index.ts:139-152 (registration)
    Tool metadata and input schema registration in ListToolsRequestHandler response.
    {
      name: "get_project_details",
      description: "Get detailed information about a specific project including all fixtures, scenes, and cue lists. This returns a lot of data and should only be used when you need comprehensive project information.",
      inputSchema: {
        type: "object",
        properties: {
          projectId: {
            type: "string",
            description: "Project ID to get details for",
          },
        },
        required: ["projectId"],
      },
    },
  • Helper function to compute merged DMX channel ranges for fixtures within a universe, used in getProjectDetails for fixture summaries.
    private calculateChannelRanges(fixtures: any[]): string {
      if (fixtures.length === 0) return 'None';
    
      const ranges: Array<{ start: number; end: number }> = [];
    
      fixtures.forEach(fixture => {
        const start = fixture.startChannel;
        const channelCount = fixture.channelCount;
        const end = start + channelCount - 1;
    
        // Check if this range can be merged with the last one
        if (ranges.length > 0) {
          const lastRange = ranges[ranges.length - 1];
          if (start <= lastRange.end + 1) {
            // Extend the last range
            lastRange.end = Math.max(lastRange.end, end);
            return;
          }
        }
    
        // Add new range
        ranges.push({ start, end });
      });
    
      return ranges.map(r => r.start === r.end ? `${r.start}` : `${r.start}-${r.end}`).join(', ');
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states 'Get detailed information,' implying a read-only operation, but doesn't specify what details are included, if authentication is required, or how errors are handled. This is a significant gap for a tool with no 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 purpose without unnecessary words. It's front-loaded and appropriately sized for a simple retrieval tool, with no wasted content.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'detailed information' includes, potential return formats, or error conditions. For a tool in a context with many siblings and no structured output, more context is needed to guide effective use.

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?

The input schema has 100% description coverage, with 'projectId' documented as 'Project ID to get details for.' The description adds no additional parameter semantics beyond this, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate.

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 verb ('Get') and resource ('detailed information about a specific project'), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'list_projects' or 'create_project', which would require specifying it retrieves existing project details rather than listing or creating.

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 a project ID), exclusions, or comparisons to siblings like 'list_projects' for overviews or 'create_project' for new projects, leaving usage context unclear.

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