Skip to main content
Glama

OBS stream control

obs_stream_control

Generate a TouchDesigner control rig for OBS WebSocket to manage streaming, recording, and scene switching with dedicated CHOP channels and an automated dispatcher.

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.
Behavior5/5

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

The description discloses a critical behavioral trait beyond annotations: tdmcp never stores OBS passwords and requires manual Identify authentication if enabled. This adds specific security context that annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false) do not convey.

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 appropriately sized and front-loaded with the main purpose. It packs technical specifics (op:6 requests, component names, auth caveat) without extraneous filler, ensuring every sentence earns its place.

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?

For a complex tool with 9 parameters and no output schema, the description covers core components, command types, and an important authentication caveat. It does not mention execution defaults like auto_connect, but the schema already documents that behavior, so completeness is strong overall.

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%, and the description does not add additional parameter meaning beyond what the schema already provides. The baseline of 3 applies because the schema does the heavy lifting for parameter explanations.

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: 'Create an OBS WebSocket v5 control rig in TouchDesigner.' It lists specific components (websocketDAT, Constant CHOP, chopExecute DAT) and concrete commands (StartStream, StopStream, ToggleStream, etc.), making it distinct from sibling tools like connect_obs_recorder that focus on recording only.

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?

The description implies usage for building a complete OBS control rig in TouchDesigner, providing clear context. However, it does not explicitly mention alternatives or when not to use this tool, so it falls short of a 5.

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/Pantani/tdmcp'

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