Skip to main content
Glama

Create vector lines

create_vector_lines

Build a vector-line system from an image frame: prepare a mask, trace it into editable geometry, and composite a clean line-art overlay.

Instructions

Build a pulse-driven image-to-vector-lines system: capture a still frame from a synthetic, camera, file, or existing TOP source, prepare a monochrome mask, freeze it to a snapshot, trace it through a Trace SOP for editable vector geometry, generate a clean TOP line-art overlay, and composite it over the source. Phase 1 is intentionally not realtime: the artist presses the Vectorize pulse to update trace1/frozen_frame, keeping cook cost bounded. Source defaults to a static synthetic contour card so it previews without camera permissions or moving noise; camera is opt-in. Exposes Vectorize, Threshold, PreBlur, StepSize, Smooth/Fit/Border toggles, line color/width, opacity, overlay mode, and calibration knobs. Returns the container, source/prep/frozen/trace/vector/output paths, warnings for unverified Trace/snapshot details, and a preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoPrep mode: foreground-oriented mask, mask-only, or full_frame edge/detail tracing.hybrid_foreground
nameNoName for the vector-line system COMP.vector_lines
invertNoInvert the prepared mask before tracing.
sourceNoImage source. 'synthetic' is the safe default; 'camera' is opt-in; 'file' reads movie_file_path; 'existing_top' pulls existing_top_path through a Select TOP.synthetic
opacityNoOpacity of the rendered vector overlay.
pre_blurNoBlur amount before thresholding/tracing to remove camera noise.
resampleNoResample Trace SOP shapes to reduce excessive point density.
step_sizeNoTrace SOP resample step / simplification amount.
thresholdNoBrightness/mask cutoff for the prep image and Trace SOP.
fit_curvesNoFit Trace SOP output to Bezier curves; off by default until live-probed.
line_colorNoVector material color as '#rrggbb'.#49dcb2
line_widthNoWireframe line width where supported by the material.
parent_pathNoParent COMP where the system container is created./project1
show_sourceNoComposite the source image under the vector layer when true.
overlay_modeNoComposite TOP operand when show_source=true.over
camera_deviceNoOptional camera device name for source='camera'.
smooth_shapesNoSmooth traced shapes to reduce sharp camera-noise corners.
remove_bordersNoRemove dirty image borders in Trace SOP when supported.
expose_controlsNoExpose the Vectorize pulse plus prep/look/calibration controls.
movie_file_pathNoMovie/image path used when source='file'.
existing_top_pathNoExisting TOP path used when source='existing_top'.
analysis_resolutionNoCapture/trace resolution [width, height] that bounds vectorization cost.
Behavior5/5

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

The description discloses key behavioral traits beyond annotations: the non-realtime pulse-driven nature, intentional cook cost bounding, default source behavior to avoid camera permissions, and that camera is opt-in. It also states it returns warnings for unverified details. This adds significant context over the basic readOnly/destructive hints.

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, information-dense paragraph with four sentences, each adding essential context: pipeline, non-realtime constraint, source defaults, exposed controls, and return values. It is long but proportionate to the tool's 22 parameters, and every 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?

Given 22 parameters and no output schema, the description is remarkably complete: it explains the full workflow, the phase boundaries, default source rationale, control exposure, and return values (container, paths, warnings, preview). The schema covers individual parameters, and the description ties them together effectively.

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, but the description adds value by naming exposed controls (Vectorize, Threshold, PreBlur, StepSize, Smooth/Fit/Border, line color/width, opacity, overlay mode) and explaining source defaults and camera opt-in, which enriches the meaning of the source and control parameters.

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 opens with 'Build a pulse-driven image-to-vector-lines system' which is a specific verb+resource that clearly differentiates it from sibling tools. It details the full pipeline (source capture, mask, snapshot, Trace SOP, overlay, composite), leaving no ambiguity about what the tool creates.

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 usage context: it is intentionally non-realtime, uses a default synthetic source for safe preview, and camera is opt-in. It implicitly warns against realtime use by noting the Vectorize pulse bounds cook cost, but it does not name explicit alternative tools or state when not to use this tool.

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