Skip to main content
Glama

Picture to SVG

vectorize

Turns a picture into a vector SVG with Recraft (charged in credits, see list_models tools). Give job_id of one of your genframe pictures, or image_url (public https, JPG/PNG/WebP, sides 256–4096 px).

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
proNoRecraft Pro vectorizer (more detail, more credits).
job_idNo
image_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-read-only, open-world, non-idempotent, non-destructive), the description discloses the credit cost and points to list_models for pricing, plus input format and resolution limits. It stops short of saying where the resulting SVG is returned or stored, which matters for a generating tool.

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 tight sentences, front-loaded with the action and followed by the two input options. The parenthetical pricing pointer is useful but slightly interrupts the flow.

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

Completeness3/5

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

For a generative tool with no output schema, the definition never says what comes back — a URL, an inline SVG, or a job reference — nor how credit consumption is reported. Input-side guidance is strong, so the omission is noticeable but not crippling.

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 only 33%, and the description compensates well: it explains that job_id must reference one of the caller's own genframe pictures, and details the accepted form of image_url that the bare schema leaves out. The only gap is that the pro flag's trade-off is left to the schema's own text.

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?

The description gives a specific verb and resource ("Turns a picture into a vector SVG") and names the underlying engine (Recraft). It is clear what the tool produces, though it does not explicitly contrast itself with siblings like upscale_image or remove_background, which also transform images.

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?

It spells out the two mutually exclusive input routes: a genframe job_id or a public image_url, with constraints on the URL (public https, JPG/PNG/WebP, 256–4096 px sides). It does not say when to prefer this over other image-processing siblings, but the input alternatives are explicit.

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.

Resources