VecSnap Image to SVG

Vectorize an image to SVG

vectorize_image

Idempotent

Use this when the user wants an image converted to SVG or vector (vectorize, trace, image to SVG): a logo, an icon, an illustration, a picture from an AI tool. It converts an image the user already has, and does not create new images. Pass the image as a file, or a public https link, and never a file name or made-up data. If you cannot pass it as either, call this with neither: a card in the chat lets them drop it, or the answer says where they can. It answers the conversion's figures and page_url, the person's VecSnap page. Converting is free; the file costs one credit, once per image, and the person saves it from the card or that page. Where a card shows, it holds the drawing, its figures and its cost. With no card, page_url is the person's way to the result.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vectorize_image"
  }
}

Input Schema

Name	Required	Description
`url`	No	A public https link to the image, when there is no file.
`image`	No	The image file from this chat.
`preset`	No	How to draw it. Leave it out for filled shapes (default). centerline draws each line of the drawing as one single line instead of an outline: for line art or a sketch when the user asks for centerline, single line or one-stroke paths, or for it to be drawn by a pen plotter, a Cricut pen, foil or a scoring blade. A filled logo stays filled, for cutting or engraving too, unless the user asks for single lines.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: the credit model (conversion free, file costs one credit, charged once per image), what the response answers (the conversion's figures and page_url), and the card-vs-no-card delivery paths. The 'once per image' credit statement usefully reinforces the idempotentHint=true annotation rather than contradicting it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded correctly with the trigger condition, then input rules, then outputs and cost. However, the closing two sentences about the card and page_url restate what the earlier sentence ('saves it from the card or that page') already said, and the phrasing ('its figures', 'the person's way to the result') is indirect enough to slow comprehension.

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?

Covers the essentials for a charging, open-world conversion tool with no output schema: inputs allowed, fallback path, cost, and the returned page_url and figures. It does not describe what the user actually receives in the SVG (e.g. shape fidelity, size, or file naming), a minor gap given there is no output schema to fill it.

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; the description earns extra by constraining input form ('a file, or a public https link, and never a file name or made-up data') and by validating the zero-argument case. It adds no guidance on the preset/centerline choice, but the schema already documents that thoroughly.

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 (convert an image to SVG/vector) and explicitly bounds the scope with 'It converts an image the user already has, and does not create new images', which cleanly separates it from any image-generation sibling. Trigger synonyms (vectorize, trace, image to SVG) are given so an agent can match user phrasing.

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?

Gives a clear when-to-use condition plus an explicit fallback policy: if the image cannot be passed as a file or public https link, 'call this with neither' so the chat surfaces an upload card. It also warns against passing a file name or fabricated data. It stops short of naming which sibling to use for retrieval of an existing result (e.g. fetching a finished SVG), so the alternative-routing guidance is incomplete.

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

All VecSnap Image to SVG tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?