Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

vectorize_image

Convert raster images on a canvas into editable vector paths, turning PNG/JPEG imports and screenshots into editable shapes. The original raster element stays intact.

Instructions

Convert a raster image element on the canvas into editable vector paths. The new vector elements are placed on the canvas; the original raster element is left untouched (delete it manually if no longer needed). Use for: importing PNG/JPEG content the user wants to edit as vectors, cleaning up screenshots into icons, or converting AI-generated raster images into editable shapes. Requires Quiver API key.

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": {
      "canvasId": "<canvasId>",
      "sourceElementId": "<sourceElementId>"
    },
    "name": "vectorize_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
autoCropNoAuto-crop the source image before vectorizing (default true).
canvasIdYesCanvas ID. Required.
sessionIdNoSession ID for per-session visual feedback. Optional.
sourceElementIdYesElement ID (or `#ref`) of the raster element to vectorize. Required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, and idempotentHint=false. The description adds genuinely useful non-annotated behavior: it creates new elements rather than mutating the source, the original raster survives and must be deleted manually, and a Quiver API key is required. It still omits what repeated calls do (implied duplication) and any failure/rate-limit behavior, so it adds value but not richly.

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?

The purpose and the key side effect are front-loaded, and the use-case list earns its space by aiding tool selection. Slightly verbose: the parenthetical about manual deletion and the three-item use list could be trimmed without losing meaning.

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 4-parameter mutation tool with full schema coverage and no output schema, the description covers purpose, use cases, side effects, and an auth prerequisite. The remaining gap is the return shape — since no output schema exists, the description could say whether the new element IDs are returned, which would help follow-up calls.

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 canvasId, sourceElementId, autoCrop, and sessionId are all documented in the schema itself. The description adds no parameter-level detail beyond reiterating that the source element is untouched; the baseline 3 applies when the schema does the heavy lifting.

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 uses a specific verb+resource ('Convert a raster image element on the canvas into editable vector paths') and states the concrete outcome (new vector elements added). It implicitly distinguishes itself from generation-style siblings by drawing on an existing canvas element, but it never names an alternative tool, so an agent must infer the routing rather than read it.

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?

The 'Use for:' list gives three concrete scenarios (importing PNG/JPEG for editing, cleaning up screenshots into icons, converting AI-generated rasters), which is stronger than most definitions. There is no explicit when-not guidance and no named alternative for generating vectors from scratch, so it falls short of a 5.

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