PerfectVector

Pick image

pick_image

Idempotent

Open PerfectVector's file picker in the chat, for a file on the user's computer.

Use it only when the chat can't pass the user's file to tools (Claude chat today) or no image was given, and the user has no link to it. If your host can't show PerfectVector's picker (a terminal, for example), don't call this: upload the file with create_image_upload_link, or pass a public link to check_price. The picker shows the price and the balance; choosing the file is the user's OK to spend 1 credit, and the picker converts it and shows the SVG with a Download button. While it is open, call nothing else and end your turn. Later, get_svg with no ID finds the result.

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

Input Schema

Name	Required	Description	Default
No arguments

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.
`next_action`	Yes	What to do next; guidance, never spending permission.
`request_key`	No
`conversion_id`	No
`price_credits`	No
`credits_charged`	No	Credits charged by this call only.
`credits_available`	No	The balance afterwards.
`retry_after_seconds`	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?

Goes well beyond the annotations: it discloses that the picker displays price and balance, that selecting the file constitutes the user's consent to spend 1 credit, that conversion and an SVG preview with Download happen inside the picker, and that the agent must call nothing else and end its turn while it is open. These are consequential side effects and coordination rules that annotations alone (readOnlyHint false, idempotent) do not convey.

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?

Three sentences, front-loaded with the core action, then gating conditions, then behavioral consequences. Dense and purposeful, though the credit/picker mechanics sentence packs several clauses and could be split for faster scanning.

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 a zero-param tool with an output schema, the description covers everything an agent needs: eligibility preconditions, host limitations, the credit cost and consent semantics, the blocking rule, and how to retrieve the result afterward (get_svg with no ID). No behavioral gap remains.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description appropriately spends its words on workflow rather than inventing parameter detail.

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?

States a specific verb and resource — opening PerfectVector's in-chat file picker for a file on the user's computer — and contrasts itself with create_image_upload_link and check_price, so an agent can tell it apart from siblings without opening any schema.

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?

Gives explicit when-to-use ('only when the chat can't pass the user's file to tools or no image was given, and the user has no link') and explicit when-not ('if your host can't show the picker, e.g. a terminal, don't call this'), plus named alternatives (create_image_upload_link, check_price) for the fallback path.

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?