Skip to main content
Glama
Sign In
imagetosvg-mcp

imagetosvg-mcp

by ujo78
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Convert image to SVG

convert_image_to_svg

Vectorize raster images (PNG, JPG, etc.) into editable SVGs. Choose auto, simple, or layered mode based on image complexity.

Instructions

Vectorize a raster image (PNG/JPG/WebP/GIF/BMP/TIFF/AVIF) into an editable SVG. mode=auto picks simple vs layered by image complexity. Returns a summary and an inline PNG preview.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input_path": "<input_path>"
    },
    "name": "convert_image_to_svg"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_pathYes
modeNo
max_colorsNo
output_pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Mentions mode selection and return of summary and preview, but lacks details on important traits like color handling, size limits, or potential side effects. No annotations present to compensate.

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?

Two sentences with front-loaded purpose. Efficient but could be slightly more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Missing explanation for two parameters and lacks details on return value contents beyond summary and preview. Incomplete for effective tool use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description covers input formats and mode but does not explain 'max_colors' or 'output_path'. With 0% schema description coverage, the description should provide more parameter context.

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?

Clearly states the verb 'vectorize' and the resource 'raster image into an editable SVG'. Differentiates from sibling tools like edit_svg or import_vector.

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?

Implies usage when a raster image needs conversion to SVG, but provides no explicit guidance on when to choose this over alternatives like import_vector.

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