Skip to main content
Glama

Create histogram scope

create_histogram_scope

Build a luminance or per-channel RGB histogram scope for any TOP video source. GPU-based computation outputs a Null TOP for preview or binding.

Instructions

Build a luminance (and optional per-channel RGB) histogram video scope for any TOP. Computes the histogram on the GPU using a GLSL TOP (bins×1 output), samples into a CHOP, normalises, and renders through choptoSOP → renderTOP. Output is a single Null TOP ready for previews or bind_to_channel. Implements the roadmap Milestone 2 histogram scope panel as a standalone focused tool. This is the single-scope, working histogram (the one create_video_scopes can't render in TD 099); for a combined waveform/parade/vectorscope monitor use create_video_scopes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
binsNoNumber of histogram bins (16..512). Drives the GLSL TOP output width. Changing after build requires a rebuild.
gainNoPre-scope brightness (Level TOP brightness1 parameter).
modeNoHistogram mode. 'luma' = single luminance trace. 'rgb' = three overlaid per-channel traces. Note: rgb mode is informational only in v1 — ships as luma with rgb flag in extra.luma
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 — may hang TD on a macOS permission modal.test_pattern
bar_styleNoReserved — informational only in v1. Both values currently emit the same `choptoSOP`-fed render (a thin vertical strip per bin); a true polyline 'line' mode is planned. Setting this changes the value recorded in `extra` but does not yet change the SOP topology.bars
log_scaleNoCompress tall peaks with log(1+x) in the normalisation Math CHOP. Changing after build requires a rebuild.
resolutionNoOutput Null TOP size [width, height].
parent_pathNoParent COMP path; the histogram scope container is created as 'histogram_scope' inside it./project1
trace_colorNoPhosphor tint colour for luma mode as a hex string. Ignored when mode='rgb'.#00ff88
expose_controlsNoBind live controls: Gain, TraceColor (luma mode), LogScale (informational).
video_file_pathNoVideo/image file path (source='file').
existing_top_pathNoPath of an existing TOP to scope (source='existing_top').
Behavior4/5

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

Annotations (readOnlyHint=false, openWorldHint=true) set a low bar; description adds value by explaining the GPU pipeline, output as Null TOP, parameter rebuild restrictions (bins, log_scale), and the informational-only nature of bar_style. Also warns of potential hang with device source. No contradictions with 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?

Three sentences: purpose, pipeline, differentiation. No filler. Every sentence contributes meaning. Front-loaded with the core action. Ideal conciseness for the complexity.

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 12 parameters, no output schema, and the complexity of building a histogram scope, the description is comprehensive. It covers technical approach, output type, sibling tool comparison, and known limitations. Could detail the output's format more, but sufficient for agent context.

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?

Schema coverage is 100%, so baseline is 3. Description adds context beyond schema for some parameters: 'changing after build requires rebuild' for bins and log_scale, and 'reserved—informational only' for bar_style. This extra detail justifies a 4.

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?

Clearly states it builds a luminance and optional RGB histogram video scope for any TOP. Distinguishes from sibling create_video_scopes by noting it's the single-scope working histogram that the other cannot render, establishing a unique identity.

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?

Explicitly says when to use this vs the alternative create_video_scopes for combined monitors. Provides context for source types (e.g., device may cause macOS permission modal). Could add more when-not-to-use scenarios, but the guidance is clear and helpful.

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