PerfectVector

Convert to SVG · uses 1 credit

convert_to_svg

Idempotent

Turns your image into an SVG. Uses 1 credit.

image: the name check_price returned, such as "logo.png · 1 credit". It converts only an image whose price an earlier check_price call returned, in the last 30 minutes; otherwise nothing is charged and the reply says to check the price first. Set always=true only when the user answered "Yes, always". It waits about 20 seconds and returns the facts, a 24-hour download link and, for a small SVG, its text. It costs 1 credit when the SVG is delivered, once; failures are free. If it says the image is still converting, call it again with the same image: that finishes it and never charges twice.

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": {
      "image": "<image>"
    },
    "name": "convert_to_svg"
  }
}

Input Schema

Name	Required	Description	Default
`image`	Yes	The name check_price returned, such as "logo.png · 1 credit".
`always`	No	Only when the user answered "Yes, always".

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

A4.8/5.0

Behavior5/5

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

Annotations already state `readOnlyHint=false`, `idempotentHint=true`, and `destructiveHint=false`; the description adds substantial context beyond that, including the 1-credit charge timing, free failures, roughly 20-second wait, 24-hour download link, and the no-double-charge retry behavior.

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 description is front-loaded with the core action and cost, and most sentences carry operational detail. There is slight redundancy because 'Uses 1 credit' repeats the title and first sentence, but the overall structure remains efficient.

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?

Given the presence of an output schema, the description need not fully document return values, yet it still explains the returned facts, download link, and SVG text for small results. It also covers pricing, timing, retry behavior, and the required prior `check_price` workflow.

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, but the description adds workflow meaning: `image` must be a name returned by `check_price` within 30 minutes, and `always` is only for when the user answered 'Yes, always.' It reinforces rather than merely repeats the schema definitions.

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?

The description states a specific verb and resource: 'Turns your image into an SVG.' It also distinguishes the tool from siblings by tying it to a prior `check_price` call and explaining the conversion workflow, so an agent can identify it independently.

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?

It gives explicit preconditions: the image must be one whose price an earlier `check_price` call returned within the last 30 minutes, otherwise nothing is charged and the reply directs the user to check price first. It also explains the exact condition for `always=true` and what to do if the image is still converting.

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?