Skip to main content
Glama

Create capture loop

create_capture_loop

Build a bidirectional video bridge to another app, receiving an external feed and/or publishing a TOP. Supports NDI, Syphon, Spout for cross-application video sharing.

Instructions

Build a bidirectional inter-app video bridge to another program (Resolume, OBS, MadMapper, a game engine…) in one container: receive an external feed IN and publish a TOP OUT at the same time. Picks the right operators per protocol — NDI (network, macOS & Windows), or Syphon (macOS) / Spout (Windows). direction 'in' only subscribes, 'out' only publishes, 'both' runs a full round-trip loop. The receive half is a receiver TOP → Null 'in_out'; the send half pulls source_top through a Select TOP into a publisher TOP. ANTI-FEEDBACK: the two halves are never wired together, so 'both' won't loop this app's own output back in. PLATFORM-GATED & largely UNVERIFIED-live: Spout needs Windows, Syphon needs macOS, and sender/receiver-name parameter names vary by TD build (probed at runtime) — the wrong platform or a real signal needs the actual sender present. This is the combined in+out version of create_live_source (in) and setup_output (out).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoBase name for the container COMP that holds the in/out bridge.capture_loop
protocolNoInter-app video transport. ndi works on macOS & Windows (network). spout is Windows-only; syphon is macOS-only — both use the same Syphon/Spout TOPs in TouchDesigner (PLATFORM-GATED: the wrong platform fails to create the op, reported as a warning).ndi
directionNoin: only receive an external feed. out: only publish a TOP. both: do both at once (a full round-trip loop to another app, e.g. send to Resolume and receive its output back).both
resolutionNoWorking resolution [w, h] applied to the receiver TOP (Output Resolution = Custom). The publisher inherits its input TOP's resolution.
source_topNo(out) Path of the TOP to publish when direction includes 'out' (e.g. '/project1/final'). Empty together with an 'out' direction publishes nothing and is flagged as a warning.
parent_pathNoCOMP to build the capture-loop container in (e.g. '/project1')./project1
sender_nameNo(out) The public name THIS app publishes its feed under, so the other app can find it. Used for direction 'out'/'both'.tdmcp_out
receiver_nameNo(in) The name of the EXTERNAL sender to subscribe to. Empty = pick the first available sender on the network/machine. Used for direction 'in'/'both'.
Behavior5/5

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

Annotations only say readOnlyHint=false, openWorldHint=true, destructiveHint=false. The description adds substantial behavior: anti-feedback wiring (two halves never wired together), platform gating, runtime probing of parameter names, and warning about unverified live behavior. It clearly explains what the tool does internally, which is well beyond annotations.

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?

The description is about 170 words, which is detailed but not overly long given complexity. It is front-loaded with purpose, then flows through mechanics, warnings, and comparison. A few technical details (like 'receiver TOP → Null') are dense and could be clearer, but overall each sentence earns its place.

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?

For a tool with 8 params, no output schema, and open-world hints, the description thoroughly covers purpose, internal wiring, platform constraints, warnings, and relationship to siblings. It leaves little ambiguity about when and how to use it, making it highly complete given the tool's complexity.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds high-level meaning beyond schema: it explains how direction 'both' creates a round-trip, how resolution is applied, that publisher inherits resolution, and the anti-feedback logic. It ties parameters to the overall bridge behavior, which enriches understanding beyond the individual property descriptions.

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 builds a bidirectional inter-app video bridge, with specific mention of receive (IN) and publish (OUT) functionality. It explicitly distinguishes itself from create_live_source and setup_output, and names the sibling tools it combines.

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

Usage Guidelines5/5

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

Explicitly explains when to use: for inter-app video bridging to programs like Resolume, OBS, etc. It contrasts with create_live_source (in) and setup_output (out), and warns about platform-specific requirements (Spout/Syphon/NDI) and unverified live behavior, helping the agent choose appropriately.

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