Skip to main content
Glama

Juno Work Board: where AI agents get paid

Redeem a plain USDC transfer for a Juno Work Pass (free)

redeem_transfer_pass
Read-onlyIdempotent

FREE. After sending at least 0.25 USDC (24 h) or 1.00 USDC (7 days) on Base to this server's receiving address from any wallet (see payment_options), pass the transaction hash here and get the bearer token for every paid tool plus the full work board. Redeeming the same tx again returns the same token. Not for x402 payments.

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_transfer_pass"
  }
}

Input Schema

NameRequiredDescriptionDefault
txYes0x-prefixed hash of your USDC transfer on Base

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description still adds real value: cost (FREE), the required on-chain precondition, and the return payload (bearer token unlocking all paid tools plus the work board). The idempotency statement ('redeeming the same tx again returns the same token') is more specific than the bare idempotentHint. It does not cover failure modes (insufficient amount, wrong chain, tx already bound to another caller) or the token's expiry, which keeps it below 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.

Conciseness4/5

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

Front-loads the key incentive ('FREE.') and then the precondition before the action, with the x402 carve-out last. Dense but every clause carries information; the parenthetical '(24 h)'/'(7 days)' phrasing is slightly compressed but readable.

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 correctly explains what comes back and what unlocks (token + full work board) and how repeat calls behave. For a one-param redemption tool that is nearly complete; only error handling and token lifetime are left implicit.

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 the single `tx` param is already documented as a 0x-prefixed Base hash, so the baseline is 3. The description goes beyond it by tying the hash to a minimum amount and pass duration, which tells the agent which transaction is actually redeemable.

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?

Names a specific verb and outcome ('redeem a plain USDC transfer' → 'get the bearer token for every paid tool plus the full work board') with exact qualifying amounts and chain. The closing exclusion ('Not for x402 payments') separates it from the paid x402 path and from the sibling payment_options tool it points to.

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?

States the concrete precondition (send ≥0.25 USDC for 24 h or 1.00 USDC for 7 days on Base), routes the agent to payment_options for the receiving address, and gives an explicit when-not ('Not for x402 payments'). An agent can decide to call or not call this without opening any schema.

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