Skip to main content
Glama
jhonsu01

VectorMagic MCP Server

by jhonsu01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Vectorize image

vectorize_image

Convert bitmap images (PNG, JPG, PSD, TIFF) into editable SVG, AI, EPS, PDF, DXF, or EMF vector files with automatic tracing, detail, colour, and layering options.

Instructions

Convert a bitmap image (PNG, JPG, GIF, BMP, TIFF, PSD, TGA...) into an editable vector file with Vector Magic Desktop Edition. Uses Vector Magic's fully automatic mode, then optionally changes the level of detail and colour mode, and writes SVG, AI, EPS, PDF, DXF or EMF (or a re-rendered PNG/JPG/BMP/TIF). Returns the output path, a summary of what Vector Magic detected (image type, detail, number of colours) and a preview image of the vector result. Takes ~10-30 s per image; large photos take longer. Files are never overwritten unless overwrite is true.

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
previewNoReturn a PNG preview of the vector result (as shown by Vector Magic).
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
overwriteNoReplace an existing output file. Without it, files are never overwritten.
input_pathYesAbsolute path of the image to vectorize.
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
output_pathNoAbsolute output path. Default: next to the input with the format extension (adds _2, _3... instead of overwriting).
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

A3.7/5.0
Behavior4/5

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

Adds real behavioral context beyond annotations: per-image runtime (~10-30 s, longer for photos), the non-overwrite guarantee unless 'overwrite' is true, and what the response contains (output path, detected-image summary, preview). It does not cover error/permission behaviors, but the annotations already set the safety profile (non-destructive, non-idempotent) and the description is consistent with 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?

Front-loaded with the core purpose, then layers in behavior and constraints. Dense but every sentence carries information; the format enumeration is the only slightly redundant run-on given the schema already lists formats.

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 complex 12-parameter tool with no output schema, the description supplies the missing pieces an agent needs: return payload contents, runtime expectations, and overwrite semantics. Error handling and batch-vs-single routing are the only unaddressed gaps.

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?

Schema coverage is 100%, so all 12 parameters are already documented with enums and defaults in the schema. The description only gestures at 'level of detail and colour mode' and output formats, adding no syntax or semantics beyond what the schema provides. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Convert a bitmap image into an editable vector file'), names the backing engine (Vector Magic Desktop Edition), and enumerates accepted inputs and outputs. It does not explicitly distinguish itself from the sibling vectorize_batch, so sibling differentiation is left to the singular 'image' vs 'batch' inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the described workflow (automatic mode, then optional detail/colour adjustments), which is adequate for a single-purpose conversion tool. However, there is no explicit when-to-use guidance, no mention of when to prefer vectorize_batch, and no prerequisites or failure conditions.

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