PerfectVector

Check the price (free)

check_price

Idempotent

Shows the price and your balance. Free.

Stores the image for 30 minutes at its price; never converts or charges. Give exactly one input: image (the host's file object for the user's attachment), image_url (a public https link to a PNG, JPEG or WebP, up to 5 MB), upload_id (from create_image_upload_link), or conversion_id (an earlier conversion: to retry a failed one, with a NEW request_key). A new image needs a new request_key; the same key repeats a call safely. Returns the image's name for convert_to_svg, such as "logo.png · 1 credit". When the reply says to ask, ask the user its question and wait for the answer: "Yes" means convert_to_svg, "Yes, always" means convert_to_svg with always=true. Otherwise call convert_to_svg; the app asks the user to allow it.

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

Input Schema

Name	Required	Description
`image`	No
`image_url`	No	A public https link to a PNG, JPEG or WebP.
`upload_id`	No
`request_key`	No
`conversion_id`	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.
`retryable`	No
`next_action`	Yes	What to do next; guidance, never spending permission.
`request_key`	No
`conversion_id`	No
`convert_input`	No	The image value for convert_to_svg, such as "logo.png · 1 credit".
`price_credits`	No
`credits_charged`	No	Credits charged by this call only.
`credits_available`	No	The balance afterwards.
`retry_after_seconds`	No
`ask_before_converting`	No	Ask every time: for this account, in this app.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations are present but thin (readOnlyHint=false, idempotentHint=true), and the description adds real context: the image is stored for 30 minutes, nothing is converted or charged, and reusing a request_key makes the call idempotent. This is consistent with idempotentHint=true and readOnlyHint=false (state is stored), not contradictory. Does not disclose rate limits or error 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?

Dense and front-loaded with purpose, cost, and input alternatives before the workflow detail. Some sentences (the ask-the-user script) are long and could be split, but every clause carries operational information.

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?

Covers input selection, idempotency, storage lifetime, and the confirmation handoff, and an output schema exists so return-value detail is optional (the 'logo.png · 1 credit' example is a bonus). Missing explicit routing to my_credits for pure balance checks, which is the one gap against the sibling set.

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 description coverage is only 20%, so the description must compensate and largely does: it explains each of image, image_url (public https, PNG/JPEG/WebP, 5 MB), upload_id (from create_image_upload_link), conversion_id (retry of an earlier conversion with a new request_key) and request_key reuse semantics. The oneOf/exactly-one constraint is stated in prose but not in the schema, though the sentence structure ('Give exactly one input: image, image_url, upload_id, or conversion_id') muddies whether request_key counts.

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 and resource ('Shows the price and your balance') plus a cost qualifier ('Free'). It does not explicitly distinguish itself from the sibling my_credits, which plausibly also reports balance, so differentiation is left implicit.

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?

Gives concrete input-selection rules ('Give exactly one input'), retry guidance for conversion_id with a NEW request_key, and an explicit branching script for the ask-the-user reply ('Yes' → convert_to_svg, 'Yes, always' → always=true). Lacks explicit when-not/alternative routing versus my_credits or vectorize_image.

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?