tdmcp

Connect VDMX workspace

connect_vdmx_workspace

Create a VDMX OSC/Syphon workspace scaffold with configurable layer, clip, preview, and setup maps for TouchDesigner integration.

Instructions

Create a VDMX OSC/Syphon workspace scaffold with layer, clip, preview, and setup maps.

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_vdmx_workspace"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	Generated baseCOMP name.	vdmx_workspace
`active`	No
`send_port`	No
`vdmx_host`	No		127.0.0.1
`clip_count`	No
`layer_count`	No
`parent_path`	No	Parent COMP for the VDMX scaffold.	/project1
`preview_mode`	No		syphon_spout
`receive_port`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.13.1Aug 2, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=false, openWorldHint=true, and destructiveHint=false, which covers the safety profile. The description adds a bit of context by mentioning OSC/Syphon and scaffold maps, but it does not detail side effects, required permissions, or the nature of the created workspace.

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?

A single, front-loaded sentence with no filler. It efficiently conveys the core function and key artifacts, making it easy to parse at a glance.

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?

For a tool with 9 parameters, no output schema, and low schema coverage, the description is too sparse. It does not clarify return values, the meaning of 'maps,' or how the parameters affect the scaffold, leaving significant gaps for the agent.

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 22% (2 of 9 parameters have descriptions), so the description must compensate. It mentions 'layer, clip, preview, and setup maps' which loosely relates to layer_count, clip_count, and preview_mode, but it does not clarify ports, host, active, or parent_path semantics.

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 clearly states the action ('Create') and the resource ('VDMX OSC/Syphon workspace scaffold'), including specific components like layer, clip, preview, and setup maps. This distinguishes it from sibling tools about other platforms or workflow elements.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or comparison with similar tools such as connect_resolume_arena or scaffold_vj_deck.

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

Deploy Server