Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Buy a Studio Pass (prepaid)

buy_studio_pass

PAID: $0.20 for 24 hours or $1.00 for 30 days, paid with x402 over MCP (USDC on Base). Returns a pass that makes every paid tool free until it expires. No x402 client? Send the USDC from any wallet and use redeem_pass instead (see payment_options).

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

Input Schema

NameRequiredDescriptionDefault
tierNoday = 24 hours (default), month = 30 days.
labelNoOptional label kept inside the pass (for example your agent or project name), up to 40 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations, it discloses pricing, the payment protocol and network, that the purchase is a real charge, and the ongoing effect of the resulting pass. It does not cover edge cases an agent would care about, such as what happens if a pass is already active, whether a retry could double-charge (relevant given idempotentHint=false), or what a failed payment returns.

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?

Three tight sentences, each earning its place: the lead front-loads price and mechanism, the second states the payoff, the third handles the fallback path. No filler or 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?

For a zero-required-parameter purchase tool with no output schema, the description covers cost, method, result, and fallback. The main remaining gap is what the returned pass value looks like (ID, expiry field) and what a caller should do after a purchase fails, though the sibling pass_status partially covers post-purchase checking.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both `tier` (with its enum and duration mapping) and `label` (with its 40-character limit and example) are already fully documented in the schema. The description adds only the tier pricing, which helps an agent reason about cost but does not extend parameter meaning. Baseline 3 applies.

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 (buy a Studio Pass), the exact price for each tier, the payment rail (x402/USDC on Base), and the concrete effect ('makes every paid tool free until it expires'). It also names the sibling to use instead (redeem_pass) when the caller lacks an x402 client, so it is distinguishable 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?

Explicitly says when to use this tool (to unlock paid tools) and when not to (no x402 client), routing to redeem_pass and pointing at payment_options for details. Both the alternative and the condition that selects it are stated, leaving nothing to inference.

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