Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Prices and ways to pay (free)

payment_options
Read-onlyIdempotent

FREE. Prices of every paid tool, the receiving address, and the ways to pay: per call with x402 over MCP, or once with a Studio Pass (bought with x402, or with a plain USDC transfer on Base from any wallet + redeem_pass).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, closed-world), so the bar is lower. The description still adds useful behavior beyond them: the call is free, it exposes a receiving address, and it distinguishes two payment routes (per-call x402 vs. one-time Studio Pass) plus the wallet-transfer-then-redeem path, which is genuine workflow context.

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?

A single front-loaded sentence that begins with the most decision-relevant fact ('FREE') and then lists contents. The nested parenthetical about buying/redeeming a pass is dense but does not contain filler.

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?

With no output schema, the description carries the burden of describing returns, and it does so by naming the three payloads (prices, address, payment methods). What is left slightly vague is the shape of the pricing response — e.g., whether it is per-tool granular or a summary — but nothing critical to invoking the tool is absent.

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 of 4 applies. No parameter-level explanation is missing.

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 enumerates exactly what the tool returns: prices of every paid tool, the receiving address, and the accepted payment methods. That is specific and distinguishable from siblings like redeem_pass or pass_status, though the differentiation is implied by the mention of redeem_pass rather than stated as routing guidance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Leading with 'FREE' signals there is no cost to calling this, and mentioning `redeem_pass` hints at the follow-up step for the USDC-transfer path. However, it never says explicitly when to call this versus `pass_status`, `buy_studio_pass`, or `compare_addresses`, so the agent must infer the pre-purchase informational role.

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