PerfectVector

Finish the picker's image

vectorize_image

Idempotent

Card only: PerfectVector's picker card finishes, confirms or retries the image the user chose in it.

Models: never call this; use check_price, then convert_to_svg. It converts only images chosen in the picker, or, for chats that still list PerfectVector's earlier tools, an image whose price an earlier call showed.

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
`image`	No
`confirm`	No
`image_url`	No	A public https link to a PNG, JPEG or WebP.
`upload_id`	No
`request_key`	No
`conversion_id`	No
`dont_ask_again`	No

Output Schema

Name	Required	Description
`code`	No	Set when the call could not proceed.
`status`	No
`message`	Yes	The reply's text without its IDs and SVG text, for hosts that show only this.
`file_name`	No
`retryable`	No
`svg_bytes`	No
`path_count`	No
`svg_inline`	No	The SVG text is in the reply's text, never in these fields.
`color_count`	No
`next_action`	Yes	What to do next; guidance, never spending permission.
`request_key`	No
`download_url`	No
`conversion_id`	No
`price_credits`	No
`credits_charged`	No	Credits charged by this call only.
`credits_available`	No	The balance afterwards.
`download_expires_at`	No
`retry_after_seconds`	No
`ask_before_converting`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare non-read-only, idempotent, non-destructive, closed-world. The description adds a real behavioral scope constraint: it only converts images chosen in the picker (or previously priced), and it also reveals the card UI's confirm/retry nature. However, it says nothing about what 'confirm' toggling does, what a retry re-runs, or what a failed conversion leaves behind.

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, with the routing guidance ('never call this; use X then Y') placed before the eligibility caveat. The only waste is the unexplained 'Card only:' opener.

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?

An output schema exists so return values need not be described, but for a 7-parameter tool with 0 required parameters and 14% schema coverage, the agent is left to guess how to actually invoke it. The description also never clarifies that despite the 'never call this' line, some callers in legacy chats may still be permitted.

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?

Seven optional parameters with only 14% schema description coverage, and the description names none of them. confirm, dont_ask_again, request_key, upload_id, conversion_id, and image_url vs. image are entirely unexplained, even though the 'price shown by an earlier call' phrasing clearly relates to conversion_id/request_key. The low-coverage case requires the description to compensate, and it does not.

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?

States a specific verb set (finishes, confirms, retries) and a specific resource (the image the user chose in PerfectVector's picker card), and names the two siblings that should be used instead. The leading 'Card only:' fragment is opaque on its own, but the rest of the sentence is unambiguous.

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 says 'Models: never call this; use check_price, then convert_to_svg', naming both the exclusion and the ordered alternative path. It also states the precondition under which it may still be used (picker-chosen images, or an image whose price an earlier call already showed).

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

All PerfectVector 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?