Skip to main content
Glama

Vistas Studio: generative SVG art for agents

Redeem a USDC transfer for a Studio Pass (free)

redeem_pass
Read-onlyIdempotent

FREE. After sending at least $0.20 (24 h) or $1.00 (30 days) USDC on Base to 0x7C1F5120B22ce1Fc0E7972e68F322d40B49578aD in one transfer, give the transaction hash here to get the pass. The pass runs from the transfer's block time. Keep the pass to yourself: whoever holds it can use it until it expires. A pass redeemed from a plain transfer can be redeemed by anyone who knows that transaction hash (hashes are public on-chain), so redeem right after paying.

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": {
      "tx": "<tx>"
    },
    "name": "redeem_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYesBase transaction hash of the USDC transfer (0x + 64 hex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint, idempotentHint), but the description goes well beyond them: pass validity starts at the transfer's block time, expiry semantics, and a real security warning that anyone holding the transaction hash can redeem a plain transfer. That hash-is-public disclosure is exactly the kind of caveat annotations cannot express.

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-loads the 'FREE' qualifier and the payment threshold before the mechanics, and every sentence carries actionable information. The security point is stated twice in slightly different forms ('keep the pass to yourself' and 'can be redeemed by anyone who knows that transaction hash'), which is mild redundancy.

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 one-parameter tool whose annotations already declare read-only and idempotent behavior, the description covers prerequisites, cost, expiry, and risk. The remaining gap is that it never hints at what is returned (the pass itself, presumably a token string), which matters since there is no output schema.

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% and already documents the single 'tx' parameter format, so the baseline is 3. The description adds meaning beyond that by tying the hash to a specific chain (Base), a specific recipient address, a minimum amount, and a single-transfer constraint.

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?

Names a specific verb and resource ('Redeem a USDC transfer for a Studio Pass') and immediately signals the free path versus a presumably paid one ('FREE'), which separates it from buy_studio_pass. It stops short of explicitly naming the sibling alternative, so the distinction is implied rather than stated.

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?

Gives concrete preconditions an agent can act on: send at least $0.20 (24 h) or $1.00 (30 days) USDC on Base to a specified address in one transfer, then submit the hash. It also adds timing guidance ('redeem right after paying'), though it never states what to do if the user has not yet paid.

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