Skip to main content
Glama
bbernstein

LacyLights MCP Server

by bbernstein
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

export_data_table

Export a lighting data table (fixtures, looks, cue lists) as CSV or Excel for backup, analysis, or reporting. CSV returns inline text; Excel writes a file and returns its path.

Instructions

Export one data table (fixtures, looks, cue lists, look details, ...) as CSV or Excel.

  • format "csv" (default): returns the CSV text inline so you can read it. Large exports are truncated (default 50000 characters), preferably at a line break, with truncated=true and a note. A cut is not guaranteed to fall between complete rows (a very long first line, or a quoted field containing line breaks, may be split); pass outputDirectory to also save the full file, or raise maxCharacters.

  • format "xlsx": writes the Excel file to disk and returns its path, row count and size (no file content in the response).

Files are written to outputDirectory, else the LACYLIGHTS_EXPORT_DIR environment variable, else a private lacylights-exports folder in the system temp directory. Existing files are never overwritten; a numeric suffix is added instead. Use list_data_export_tables to see the tables and which need scopeId.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesTable to export (case-insensitive): FIXTURE_TYPES, FIXTURE_LIBRARY, FIXTURES, LOOKS, LOOK_DETAILS, EFFECTS, LOOK_BOARD_ENTRIES, CUE_LISTS or CUE_LIST_DETAILS. See list_data_export_tables for what the connected backend supports.
formatNo"csv" (default) or "xlsx", case-insensitive. csv returns text inline; xlsx writes a file and returns its path.csv
scopeIdNoLook ID for LOOK_DETAILS, cue list ID for CUE_LIST_DETAILS, optional look board ID for LOOK_BOARD_ENTRIES.
projectIdNoProject ID. Required for every table except FIXTURE_LIBRARY.
maxCharactersNoCSV only (ignored for xlsx): maximum characters returned inline (default 50000).
outputDirectoryNoDirectory to write the file to (created if missing). For CSV, setting this also saves the full untruncated file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.6/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 truncation at a default 50000 characters with a truncated flag, that cuts may split rows, the file-write path resolution order (outputDirectory, then LACYLIGHTS_EXPORT_DIR, then temp), and that existing files are never overwritten but get a numeric suffix.

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?

Front-loaded with the core action and split into scannable bullets, with the format distinction up top. It is somewhat long, but nearly every clause (truncation edge cases, path resolution, overwrite policy) carries decision-relevant information.

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?

With no output schema and no annotations, the description fully compensates by describing return shapes for both formats (inline CSV text vs. a path/row-count/size for xlsx). 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 already 100%, but the description adds real meaning: it explains the csv/xlsx behavioral difference per format, that maxCharacters is CSV-only and ignored for xlsx, and that setting outputDirectory for CSV also saves the full untruncated file.

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 ('Export one data table ... as CSV or Excel') and enumerates the exportable tables. It is clearly distinguishable from sibling exporters export_data_workbook and export_eos_ascii by scoping to a single table.

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?

Routes the agent to list_data_export_tables to discover available tables and which need scopeId, and explains the csv-vs-xlsx choice. It stops short of explicitly contrasting with export_data_workbook, so the alternative-selection guidance is implied rather than stated.

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