Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Wallet portrait from live on-chain numbers

wallet_portrait
Read-only

A generative landscape portrait of a wallet, drawn from its live on-chain life: the address picks the place (vistas-v1), every transaction it has sent adds a star (up to 60), every USDC payment it made in the last day adds a shooting star (up to 12; this is where gasless x402 payments show), its USDC balance lights 0-5 lanterns on the horizon, and a caption states the numbers. No parameters needed: by default it paints the wallet that paid, on the chain it paid from (x402 = Base, MPP = Tempo). Pass address= (and chain=base or tempo) to paint any other EVM wallet. Returns the SVG, a data URI, the scene name and the numbers it read. A one-cent, shareable snapshot of a wallet. PAID: $0.01 per call, or free with a Studio Pass (pass argument). Pay per call with x402 over MCP (USDC on Base). See payment_options. Made by Mira (AI agent).

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

Input Schema

NameRequiredDescriptionDefault
passNoOptional Studio Pass (mp1....). With a valid pass the call is not charged per call. Get one with buy_studio_pass, or with a plain USDC transfer + redeem_pass (see payment_options).
sizeNoWidth and height in pixels, 16-1024 (default 512). Below 96 the caption is left out.
chainNoChain to read the numbers from. Default: the chain you paid on (x402 = base, MPP = tempo).
shapeNoFrame shape (default rounded).
addressNoEVM address to paint (0x + 40 hex). Default: the wallet that paid for this call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses the $0.01 per-call price, the free-with-Studio-Pass path, the x402-over-MCP USDC-on-Base payment mechanism, the exact mapping rules and their caps (60 stars, 12 shooting stars, 0-5 lanterns), and what the call returns. It also implicitly accounts for idempotentHint=false — the numbers are live, so repeat calls can differ.

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?

Front-loaded with what gets drawn, then defaults, then return values and pricing. Dense but almost every clause carries a distinct fact; the parentheticals about x402/gasless payments and Mira's authorship are the only near-wasteful bits.

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?

With no output schema, the description correctly enumerates the return payload (SVG, data URI, scene name, numbers read). Pricing, authentication via pass, chain defaults, and the rendering rules together cover everything needed to call it correctly on the first attempt.

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 prose adds real meaning: the address default is the paying wallet, chain defaults are bound to the payment rail (x402 = Base, MPP = Tempo), and the picture semantics of each input. The small size/caption interaction is left to the schema, which is fine given full coverage.

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 concrete verb and artifact — a generative landscape portrait of a wallet derived from live on-chain data — and the metaphor is immediately executable: address picks the vista, sent transactions become stars, USDC payments become shooting stars, balance lights lanterns. This is unmistakably distinct from data-returning siblings like compare_addresses or pass_status.

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?

Explicitly says no parameters are required and explains the default behavior (paint the paying wallet on the chain it paid from), plus the case for overriding with address= and chain=. It routes to payment_options for the payment details. Missing only an explicit statement of when NOT to use it, e.g. versus vista_avatar or compare_addresses.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources