Skip to main content
Glama
presign-guard-wallet-mcp

presign-guard-wallet-mcp

Buy USDC with a card

buy_usdc

Generate a 5-minute Coinbase checkout link so your owner can buy USDC with a card, Apple Pay, or Google Pay and send it to your Base wallet when funds are low.

Instructions

When this wallet has no or too little USDC and your owner has no crypto: get a Coinbase checkout link where they buy USDC with a card, Apple Pay or Google Pay; Coinbase sends it straight to this wallet on Base. Nothing is paid by you: give your owner the link (it works for 5 minutes). Needs a wallet linked to the Fizzl wallet server.

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

Input Schema

NameRequiredDescriptionDefault
amount_usdNoDollars of USDC to buy (default 5; a few dollars is plenty for x402 calls)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.7

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare openWorldHint, so the description carries the burden and does so well. It discloses that the agent itself pays nothing, that the link expires in 5 minutes, that funds route directly to the wallet on Base, and that a wallet must be linked to the Fizzl wallet server — a prerequisite and time constraint not encoded anywhere else.

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?

A single dense sentence chain that front-loads the trigger condition before the mechanism, the expiry, the cost disclaimer, and the prerequisite. No clause is filler; each adds an operational fact the agent would otherwise have to guess.

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 one optional parameter and no output schema, the description supplies the trigger, the returned artifact ('a link'), its lifetime, the funding path, and the auth prerequisite. The only gap is what happens after the owner pays — whether the agent polls, receives a callback, or must re-check wallet_status — which would help close the loop.

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% and the single amount_usd parameter already documents default 5 and the 1–500 range. The description adds no further semantics about amount (e.g. what happens at the maximum or how the purchase amount interacts with x402 needs), so the 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 outcome: obtain a Coinbase checkout link so the owner can buy USDC with card/Apple Pay/Google Pay, delivered to this wallet on Base. The mechanism (link generation plus direct delivery to the wallet) is concrete enough that an agent can distinguish this from send_usdc or pay_x402, which presuppose existing funds.

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 an explicit trigger condition — 'this wallet has no or too little USDC and your owner has no crypto' — which implicitly rules out the transfer/payment siblings. It stops short of naming an alternative outright, so the agent must infer the fallback path when the owner does hold crypto, but the context is otherwise unambiguous.

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