PerfectVector

Check the picker's image

get_picked_image

Read-onlyIdempotent

Card only: what PerfectVector's picker shows for its key, also after a reload.

Models: never call this; use get_svg. Read-only: never converts or charges.

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": {
      "picker_key": "<picker_key>"
    },
    "name": "get_picked_image"
  }
}

Input Schema

Name	Required	Description	Default
`picker_key`	Yes

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/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, and non-destructive traits, and the description adds value beyond them: "never converts or charges" discloses that no credits are consumed (not in annotations), and "also after a reload" discloses that the result persists rather than being transient UI state. It does not mention what happens with an unknown or expired picker_key, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short lines, front-loaded with the scope constraint and followed by the audience warning; both sentences carry distinct information. No filler, no restatement of the title.

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?

An output schema exists, so return values need no explanation, and the annotations plus the charge/persistence notes cover behavior well. The remaining gap is the undocumented picker_key lifecycle (how to get or recognize a valid key, behavior on an invalid one), which the description does not address.

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?

Schema description coverage is 0%: picker_key has a strict pattern (^pk_[0-9a-f_]+$) and length bounds but no documented meaning, and the description only refers to it as "its key" without saying what a picker key is or where an agent obtains one. With a required parameter and zero schema descriptions, the description needed to compensate and largely 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?

The description states the resource (the image PerfectVector's picker shows for a given key) and its scope constraint ("Card only", persists across reloads). The verb is implicit rather than an explicit "retrieve/fetch," but an agent can still tell what the tool returns. It also names the sibling it must not be confused with (get_svg), separating it cleanly from the other tools.

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 an explicit prohibition ("Models: never call this") and an explicit alternative ("use get_svg"), which is the strongest form of routing guidance. It also states the one legitimate context ("Card only"), so an agent knows when the restriction does and does not apply. Nothing about selection is left to inference.

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?