Skip to main content
Glama

OBS stream control

obs_stream_control

Builds an OBS control rig in TouchDesigner for starting/stopping streams and recordings, and switching scenes via OBS WebSocket v5.

Instructions

Create an OBS WebSocket v5 control rig in TouchDesigner: websocketDAT connection, Constant CHOP command channels for stream/record/scene actions, and a chopExecute DAT that dispatches op:6 request payloads such as StartStream, StopStream, ToggleStream, StartRecord, StopRecord, ToggleRecord, and SetCurrentProgramScene. tdmcp never accepts or stores OBS passwords; if OBS authentication is enabled, complete Identify authentication manually in the generated obs_dispatch DAT.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNoOBS WebSocket host/IP.127.0.0.1
nameNoName of the created/reused baseCOMP.obs_stream_control
portNoOBS WebSocket port.
scenesNoOptional OBS scene names. Each creates a scene_* control that sends SetCurrentProgramScene.
use_tlsNoUse wss:// instead of ws://.
parent_pathNoParent COMP to build the OBS control rig in./project1
auto_connectNoStart the websocketDAT active immediately. Defaults false for show safety.
auth_requiredNoSet true only as a reminder that OBS WebSocket authentication must be completed manually; tdmcp never stores an OBS password.
include_recordingNoAlso create StartRecord, StopRecord, and ToggleRecord controls.
Behavior4/5

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

Annotations say readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds meaningful context beyond these: it discloses the authentication limitation ('tdmcp never accepts or stores OBS passwords') and instructs manual Identify completion, which is not covered by annotations. It also specifies WebSocket v5 and op:6 request payloads, giving the agent insight into the underlying mechanics.

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 two sentences, front-loaded with the core action and resource. It includes an actionable list of commands and an important security caveat. Every sentence earns its place without unnecessary words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of generating a control rig and the absence of an output schema, the description covers the main deliverable (components), supported commands, and the critical authentication requirement. It does not explain the post-generation workflow or lifecycle, but the schema handles parameter context, so the information is sufficient for an agent to understand the tool's scope.

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% with all 9 parameters documented. The description does not add parameter-specific details beyond what is in the schema; it reinforces the role of scene and record controls but does not introduce new semantics. Baseline 3 is appropriate when schema carries the descriptive burden.

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 tool's purpose: creating an OBS WebSocket v5 control rig in TouchDesigner. It specifies the exact components (websocketDAT, Constant CHOP, chopExecute DAT) and enumerated commands (StartStream, StopStream, ToggleStream, StartRecord, StopRecord, ToggleRecord, SetCurrentProgramScene), making it distinct from sibling tools like connect_obs_recorder or create_control_surface. The verb 'Create' is specific and the resource is well-defined.

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 for building an OBS control rig but does not explicitly state when to use this tool versus alternatives. There is no mention of when not to use it or a comparison with siblings such as connect_obs_recorder. The context is clear but exclusions and alternative guidance are missing.

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

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/lucasmaher-hash/touch-designer-mcp'

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