Skip to main content
Glama

Vectorize an image

vectorize
Read-onlyIdempotent

Convert a raster image (PNG, JPG, WebP or GIF, up to 10 MB) into a vector file. Returns a rendered PNG preview of the result and the complete file source as text, ready to save as .svg, .dxf or .eps, with a download link to that file valid 24 hours. Input: image_url, a public http(s) link to the image; in ChatGPT, an image attached to the conversation arrives as the image file instead. Modes: "standard" (logos, illustrations, AI-generated art), "laser" (closed cut paths for laser cutters), "cricut" (cutting machines), "centerline" (one stroke per line: scanned drawings, line art, single-line lettering; photos and filled shapes are refused). Formats: "svg" (default), "dxf" (R12 polylines in millimetres, for laser, CNC and CAD), "eps" (print and sign-making). Very detailed images such as photos can give a file too large to return in the conversation. A conversion takes about 5 to 20 seconds. Deliver the returned file exactly as it is, saved under the given extension, or give the user the download link that comes with it: never replace it with a tracing of your own.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoTracing mode: "standard" for logos, illustrations and AI art; "laser" for closed cut paths; "cricut" for cutting machines; "centerline" for single strokes on line art and scanned drawings.standard
imageNoAn image attached to the conversation, as supplied by the host app. Omit it when passing image_url.
formatNoOutput file: "svg" (default) for design tools and Cricut Design Space; "dxf" for laser cutters, CNC routers and CAD; "eps" for print, sign-making and older design software.svg
image_urlNoPublic http(s) URL of a PNG, JPG, WebP or GIF image, up to 10 MB. Use it when no file is attached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare readOnly/idempotent/non-destructive, and the description goes well beyond them: it discloses the return payload (PNG preview plus full source text), a 24-hour download link lifetime, the failure mode for photo-like inputs (file too large to return), and an explicit fidelity instruction not to substitute its own tracing. These are exactly the operational traits an agent cannot infer from annotations.

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 purpose and input limits, then modes, then formats, then constraints - a logical progression. It is dense with useful detail, but the mode and format lists restate the schema enum descriptions nearly verbatim, which is wasted space in a description this long.

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?

There is no output schema, and the description compensates fully by describing exactly what is returned (preview image, source text, download link with expiry). Combined with input limits, timing expectations, and failure cases, an agent has everything needed to call it and handle the response 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 enum documentation is largely redundant, but the description adds value the schema does not: it clarifies the mutual exclusivity of image_url versus the attached image object in ChatGPT, and frames dxf as R12 polylines in millimetres. It does not explain the nested file object fields (file_id, download_url) beyond what the schema states.

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?

Opens with a precise verb and resource: 'Convert a raster image (PNG, JPG, WebP or GIF, up to 10 MB) into a vector file.' The accepted inputs, size limit, and output artifact are all stated up front, so an agent knows exactly what the tool produces without opening the schema.

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 maps each mode to a use case ('standard' for logos/AI art, 'laser' for closed cut paths, 'cricut' for cutting machines, 'centerline' for line art), names when 'centerline' is refused, and gives format selection criteria per downstream consumer. It also states which input path to use (image_url vs. attached file) and the expected 5-20 second latency.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.