tdmcp

Connect lighting console OSC

connect_lighting_console_osc

Create a safety-gated OSC command scaffold for grandMA3, ETC Eos, ChamSys, Avolites, or generic lighting consoles. Enables cue programming without direct DMX output.

Instructions

Create a safety-gated OSC command scaffold for grandMA3, ETC Eos, ChamSys, Avolites, or generic lighting consoles without sending direct DMX.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "connect_lighting_console_osc"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	lighting_console_osc
`active`	No
`cue_count`	No
`send_port`	No
`parent_path`	No	Parent COMP for the lighting-console OSC scaffold.	/project1
`safety_mode`	No		dry_run
`console_host`	No		127.0.0.1
`receive_port`	No
`console_family`	No		generic_osc
`executor_count`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

A3.5/5.0

Behavior3/5

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

The description adds context about safety gating and OSC-only (not direct DMX), but it does not explain what 'safety-gated' means, what side effects the scaffold creation has, or any prerequisites. Annotations (readOnly=false, openWorld=true, destructive=false) are not contradicted, but the description provides only modest additional behavioral disclosure.

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, front-loaded sentence with no redundant or filler words. It efficiently states the tool's function, scope, and key differentiator.

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?

With 10 parameters and no output schema, a one-sentence description is insufficient. It omits what the scaffold concretely produces, how parameters interact, prerequisites for use, and what the final result looks like, leaving significant gaps for an agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (2 of 10 parameters have descriptions), and the tool description itself provides no parameter-specific explanation. Terms like 'safety_mode', 'executor_count', and 'cue_count' are left to inference, so the description fails to compensate for the low schema coverage.

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?

The description uses a specific verb ('Create') and a precise resource ('safety-gated OSC command scaffold' for lighting consoles), listing supported brands (grandMA3, ETC Eos, ChamSys, Avolites, generic) and explicitly stating it does not send direct DMX. This clearly distinguishes it from sibling tools like create_dmx_fixture_pipeline.

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

Usage Guidelines3/5

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

The description implies usage when an OSC-based scaffold for lighting consoles is needed, but it does not explicitly state when to use this tool versus alternatives, nor does it give exclusions beyond the DMX note. No alternative tools are mentioned, so guidance remains implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server