Skip to main content
Glama

Create test pattern

create_test_pattern

Generate a calibration test-pattern network for projector alignment, LED mapping, or camera registration. Supports grid, crosshair, color bars, ramp, or circle-grid patterns with configurable resolution, overlay number/label, and colors.

Instructions

Generate a projector calibration / alignment source — a standalone test-pattern network that every media server ships and tdmcp was missing. Builds a baseCOMP containing a GLSL TOP with a baked-in static pattern (grid, crosshair, SMPTE-ish color bars, horizontal ramp, or circle-grid), optional text/number overlay (for per-projector ID), and a Null TOP as the stable output handle. The shader is generated per pattern and baked into the payload — no custom uniforms or live bindings needed. Use the output as a routing source during projector alignment, LED mapping calibration, or camera registration. Pattern, resolution, divisions, overlay number/label, and colours are all configurable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parent_pathNoParent COMP path to build inside (e.g. '/project1'). The container is created here./project1
nameNoBase name for the container COMP that wraps the pattern network.test_pattern
patternNoPattern type: grid = even line grid; crosshair = centred cross + corner marks; color_bars = vertical SMPTE-ish colour columns; ramp = smooth horizontal grey ramp; circle_grid = repeated concentric ring tiles.grid
widthNoOutput width in pixels (must be > 0; e.g. 1920, 2560, 3840).
heightNoOutput height in pixels (must be > 0; e.g. 1080, 1440, 2160).
divisionsNoNumber of grid cells across the frame for grid and circle_grid patterns (must be >= 1). Ignored by other patterns.
output_numberNoProjector / output ID drawn as a large label in the lower-right corner (must be >= 0). 0 = no number.
labelNoOptional extra caption text overlaid bottom-right (e.g. 'LEFT', 'CAM 2'). Empty = none.
line_colorNoPattern line colour as [R, G, B] in 0–1 range. Default is green [0, 1, 0].
bg_colorNoBackground colour as [R, G, B] in 0–1 range. Default is black [0, 0, 0].
Behavior4/5

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

The description explains that the shader is baked into the payload with no external dependencies, and the output is a stable handle (Null TOP). Annotations indicate non-destructive, open-world behavior, and the description aligns with that, adding useful context.

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 a single paragraph with concise, information-rich sentences. It front-loads the purpose and then details internals and usage. While dense, it avoids verbosity.

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 creation tool with 10 parameters and no output schema, the description adequately explains what is built and its intended applications. It provides enough context for an agent to understand the tool's role.

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 10 parameters are described in the input schema, providing full coverage. The description reiterates that parameters are configurable but adds no new meaning beyond the schema, so baseline of 3 is appropriate.

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: generating a projector calibration/alignment source with a test-pattern network. It specifies the internal structure (baseCOMP with GLSL TOP and Null TOP) and distinct use cases, setting it apart from general creation tools.

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 explicitly mentions when to use the tool: as a routing source during projector alignment, LED mapping calibration, or camera registration. However, it does not provide exclusions or compare with alternatives.

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