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 to analyze video signals. Supports multiple sources including test pattern, file, or live camera.

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?

The description discloses important behavioral traits: default source uses a test pattern (no permissions), device source may hang on macOS due to permission modal, and the histogram panel is silently skipped. These details go beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) and warn the agent about potential issues.

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 a single well-structured paragraph that front-loads the main purpose, efficiently lists panels and key technical details, and provides necessary context about siblings and source behaviors. Every sentence adds value without redundancy.

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?

The tool has 14 parameters and no output schema, but the description together with the schema covers the essential context: what the tool does, how it renders, source options, and the histogram limitation. It could mention the container creation path (though that's in the schema) for completeness, but overall it is sufficiently informative for an agent to use the tool correctly.

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

Parameters4/5

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

The input schema already has 100% description coverage for all 14 parameters, so the baseline is 3. The description adds value by explaining the purpose of the panels (waveform, parade, vectorscope), the histogram caveat, and the source behavior, which enriches parameter understanding beyond the schema.

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 broadcast-style video engineering monitor with specific scope panels (waveform, RGB parade, vectorscope). It distinguishes itself from sibling tools like create_waveform (audio) and create_histogram_scope by explicitly mentioning they are companions or alternatives.

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 gives clear context on when to use this tool: for video scopes, contrasted with audio scopes. It also warns that histogram is unsupported and recommends create_histogram_scope instead. However, it could be more explicit about when not to use this tool or prerequisites beyond the source types.

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