Skip to main content
Glama

Create video scopes monitor

create_video_scopes

Build a broadcast-style video engineering monitor with waveform, RGB parade, and vectorscope panels in TouchDesigner, using a test pattern or live video source.

Instructions

Build a broadcast-style video engineering monitor with multiple scope panels: waveform (luma trace), RGB parade (per-channel traces), and vectorscope (UV chrominance scatter). Each panel renders as a CHOP-to-SOP scope line through an orthographic camera and Render TOP, composited into a single output TOP via layoutTOP. Companion to create_waveform (audio) and create_spectrum (audio frequency). Default source is a synthetic test pattern (no device permission needed); 'device' is opt-in for live camera. The histogram panel here is unsupported in TD 099 and silently skipped — for a working luminance/RGB histogram use the standalone create_histogram_scope instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gainNoPre-scope luma gain — zooms the trace vertically (Level TOP brightness1).
layoutNoHow enabled panels arrange in the output composite.grid_2x2
sourceNoVideo source. 'test_pattern' = synthetic Banana.tif (no permission needed). 'existing_top' = reuse a TOP you already have (provide existing_top_path). 'file' = a video/image file. 'device' = live camera (videodeviceinTOP) — may hang TD on a macOS permission modal.test_pattern
parent_pathNoParent COMP path; the scopes container is created as 'video_scopes' inside it./project1
trace_colorNoPhosphor colour for scope lines as a hex string.#00ff88
enable_paradeNoShow the RGB parade panel.
enable_waveformNoShow the luminance waveform panel.
expose_controlsNoBind live controls: Gain, TraceColor, panel-enable toggles.
video_file_pathNoVideo/image file path (source='file').
enable_histogramNoShow the luma histogram panel. Currently unsupported — TD 099 has no histogramCHOP (only histogramPOP). Pass true is accepted but the panel is silently skipped; re-enable once analyzeTOP histogram mode is confirmed.
panel_resolutionNoEach scope panel's square side in pixels.
existing_top_pathNoPath of an existing TOP to scope (source='existing_top').
output_resolutionNoFinal composited TOP [width, height].
enable_vectorscopeNoShow the UV vectorscope panel.
Behavior5/5

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

Beyond annotations (readOnlyHint=false, destructiveHint=false), the description discloses meaningful behavior: the histogram panel is silently skipped in TD 099, the default source requires no device permission, and the rendering pipeline is detailed. This adds value beyond structured annotations.

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?

Four sentences, each earning its place: purpose, technical pipeline, companion distinction, and unsupported feature caveat. No filler, logically front-loaded with the core purpose.

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?

Although the tool has 14 parameters and no output schema, the description covers the essential context: what it builds, how it renders, default behavior, companion tools, and a known limitation. The rich schema handles parameter specifics.

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?

All 14 parameters have full descriptions in the input schema (100% coverage), so the description does not need to explain parameters. It adds only minimal extra context about source and histogram, which is already largely present in schema 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 states a specific action ('Build a broadcast-style video engineering monitor') with clear scope details (waveform, RGB parade, vectorscope) and distinguishes itself from sibling tools by explicitly naming create_waveform (audio) and create_spectrum (audio frequency) as companions, and directing to create_histogram_scope for histograms.

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?

Provides explicit guidance: names companion tools for audio-focused needs, points to create_histogram_scope for working histograms, explains the default test pattern source avoids permissions, and flags device as opt-in with potential macOS permission modal issues.

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