Skip to main content
Glama
jhonsu01

VectorMagic MCP Server

by jhonsu01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Vectorize several images

vectorize_batch

Vectorize multiple images in one call with shared settings, from a list or folder, writing outputs to a target directory or beside each source; one failure won't stop the batch.

Instructions

Vectorize many images in one call with the same options (one Vector Magic run per image, sequentially). Give either input_paths or input_dir (non-recursive; only supported image types are picked). Outputs go to output_dir, or next to each input. Returns one result per image; a failure does not stop the batch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorsNoauto = Vector Magic picks a reduced palette (best for logos and flat artwork). unlimited = keep every colour (photos, gradients).auto
detailNoLevel of detail. auto = what Vector Magic picks (usually high). low gives simpler shapes and smoother curves; high keeps small details.auto
formatNoOutput format. Editable vector: svg, ai, eps, pdf, dxf, emf. Bitmap rendered from the vector result: png, jpg, bmp, tif. Default svg.svg
dxf_modeNoDXF only. splines: lines + bicubic splines (smallest, most faithful). few_lines / many_lines: curves flattened into straight segments for CAD/CNC software that does not read splines.splines
input_dirNoAbsolute folder: every supported image directly inside it is vectorized.
overwriteNoReplace an existing output file. Without it, files are never overwritten.
output_dirNoAbsolute folder for the results (created if missing). Default: next to each input.
shape_modeNoHow shapes are arranged. stacked: shapes sit on top of each other (easiest to edit, no gaps). adjoining: shapes fit into cut-outs of the shapes below. adjoining_grouped: adjoining and grouped by colour.stacked
input_pathsNoAbsolute paths of the images.
show_windowNoKeep the Vector Magic window on screen while it works (debugging). By default it runs off-screen.
bitmap_scaleNoBitmap formats only: render at 1x, 2x or 4x the original pixel size.
stroke_shapesNoOutline every shape boundary with a stroke of its own colour (hides hairline gaps in some viewers).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations provide the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description only needs to add operational context. It usefully discloses sequential execution, output placement, and that one failure does not stop the batch.

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?

Four compact sentences, front-loaded with the batch behavior and followed by input/output rules. No filler, and each sentence adds operational value.

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?

With 12 fully documented parameters and no output schema, the description still covers the important batch semantics: input selection, output destinations, return shape, and failure isolation. An agent has enough context to call it 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful constraints beyond the schema: input_paths and input_dir are mutually exclusive, directory scans are non-recursive, and outputs default to sitting next to each input.

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?

States a specific verb and resource: vectorizing many images in one call. The phrase 'one Vector Magic run per image, sequentially' clearly differentiates it from the single-image sibling vectorize_image.

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?

Explains how to choose inputs ('Give either input_paths or input_dir'), that the directory scan is non-recursive, and that only supported image types are picked. It does not explicitly say when to use this versus vectorize_image, but the batch context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools