Skip to main content
Glama

Create blob trace

create_blob_trace

Trace contour of blob or silhouette from camera, movie, or synthetic source into vector line art with adjustable threshold, blur, and line width.

Instructions

Trace the contour/outline of a blob or silhouette into vector line art: source → monochrome → blur → threshold (the blob mask, optionally inverted) → optional Edge (boundary-band only) → Trace SOP (mask-to-polyline) → wireframe render. This is the CONTOUR-TRACE complement to create_vector_lines (full image vectoriser) and export_sop_to_svg, and is distinct from create_blob_reactive (which tracks blob position/reactivity — it does not draw the outline). Source can be the live camera (may prompt for macOS permission), a movie file, an animated synthetic blob (testable without a camera), or an existing TOP. Creates a new baseCOMP under parent_path. Exposes Threshold, Blur, and LineWidth controls. Returns a summary plus a JSON block with the container path, created node paths, output path, exposed controls, node errors, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
invertNoInvert the mask so dark regions become the traced blob instead of bright ones.
sourceNoBlob source. 'camera' = live webcam (may prompt for macOS camera permission). 'file' = a movie file (movie_file_path). 'synthetic' = an animated noise blob so the trace is testable with no device (the default). 'existing_top' = trace a TOP you already have (existing_top_path).synthetic
pre_blurNoGaussian blur (pixels) before thresholding — smooths noisy edges into clean contours. Live 'Blur'.
edge_onlyNoRun an Edge TOP before tracing so only the blob's boundary band is traced (hollow outline).
thresholdNoLuminance cutoff that separates blob (foreground) from background. Live 'Threshold'.
backgroundNoBackground colour behind the traced contour (RGB 0..1).
line_colorNoContour line colour (RGB 0..1).
line_widthNoContour line width for the wireframe material.
resolutionNoOutput resolution [width, height].
parent_pathNoParent network where the blob-trace container is created (default '/project1')./project1
expose_controlsNoWhen true (default), expose live Threshold, Blur, and LineWidth controls.
movie_file_pathNoPath to a movie file to trace; used only when source='file'.
existing_top_pathNoPath of an existing TOP to trace; used only when source='existing_top'.
Behavior4/5

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

Describes the pipeline steps, creation of a baseCOMP, potential macOS permission prompt, and return value. Annotations are minimal, and description adds significant behavioral context beyond them.

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?

Description is a single paragraph that front-loads purpose and pipeline, but is slightly verbose. Still efficient 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?

No output schema, but description explains return structure. With 13 parameters, the description and schema together cover the main aspects. Some edge cases (e.g., error handling) not detailed, but adequate.

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?

Input schema has 100% description coverage. Description adds overall context but does not provide additional semantics beyond what each parameter's own description already provides.

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 it traces blob contour/outline into vector line art, uses specific verbs and resources, and explicitly distinguishes from sibling tools like create_vector_lines and create_blob_reactive.

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?

Explicitly says when to use (contour tracing) vs. alternatives (full vectorization, blob reactivity) and describes source options (camera, file, synthetic, existing TOP) with context for each.

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