Skip to main content
Glama

fund_card_balance

Destructive

Load a reloadable card balance

Pay USDC to load the account holder's reloadable card balance at the card issuer.

Why this exists: the card issuer only accepts USDC on Base, and a Laso managed agent wallet holds USDC on Solana. Pay this route from either chain and Laso bridges the payment to your own deposit address at the issuer over Circle's CCTP, which burns on the source chain and mints native USDC on Base.

Price: exactly the amount you are loading, and exactly that amount is credited to the balance. Loading $50 costs $50 and puts $50 on the card. Laso covers Circle's bridging fee by burning slightly more than requested.

A linked card issuer account is required. The account holder sets it up at https://laso.finance/agent/dashboard/verified/card.

Delivery starts once your payment settles. The response confirms the payment and returns a top_up_id; the transfer to your card balance follows and usually lands in under a minute. A payment made on Base is already on the issuer's chain, so it is forwarded without a bridge. Watch the top-up under top_ups in GET /list-card-transactions, where status moves paid → bridging → delivered → credited and the transaction hash behind each leg appears as it lands, or poll GET /get-card-deposit-address until balance reflects it.

Follow with POST /create-reloadable-card to create a card against the balance once it has arrived.

If the top-up's status becomes failed, nothing is stranded: the USDC you paid has credited your Laso account balance. Retry, or recover it with POST /withdraw.

PAID ROUTE (5-10000 USD): the x402 USDC price is paid automatically from your managed agent wallet. Make sure the wallet exists and is funded first (get_agent_wallet).

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": {
      "amount": "<amount>"
    },
    "name": "fund_card_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesUSD of USDC to load onto the card balance (min $5, max $10,000). The x402 price equals this amount; Laso absorbs the bridge cost.

Output Schema

NameRequiredDescriptionDefault
noteNo
assetNo
statusNoAlways `paid` here: the payment settled and delivery to the card balance has started. Follow the later states in `GET /list-card-transactions`.
networkNo
top_up_idNoIdentifies this top-up under `top_ups` in `GET /list-card-transactions`.
funded_usdNoUSD loaded onto the card balance.
deposit_addressNoThe account holder's own deposit address at the card issuer, on Base.
payment_networkNoThe chain the payment settled on: `solana` (bridged to Base over CCTP) or `base` (forwarded directly).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / amount / description
      Previous value: -"USD of USDC to load onto the card balance (min $5, max $1,000). The x402 price equals this amount; Laso absorbs the bridge cost."New value: +"USD of USDC to load onto the card balance (min $5, max $10,000). The x402 price equals this amount; Laso absorbs the bridge cost."
    • changedInput schema / properties / amount / maximum
      Previous value: -1000New value: +10000
  2. Changed2 schema fields changed
    • removedInput schema / properties / auth_token
      Removed value: -{
      -  "description": "Laso credential. Only if the MCP connection has no Authorization header.",
      -  "type": "string"
      -}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "asset": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "deposit_address": {
      +      "description": "The account holder's own deposit address at the card issuer, on Base.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "funded_usd": {
      +      "description": "USD loaded onto the card balance.",
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "network": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "payment_network": {
      +      "description": "The chain the payment settled on: `solana` (bridged to Base over CCTP) or `base` (forwarded directly).",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "status": {
      +      "description": "Always `paid` here: the payment settled and delivery to the card balance has started. Follow the later states in `GET /list-card-transactions`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "top_up_id": {
      +      "description": "Identifies this top-up under `top_ups` in `GET /list-card-transactions`.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
      -  "properties": {
      -    "asset": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "deposit_address": {
      -      "description": "The account holder's own deposit address at the card issuer, on Base.",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "funded_usd": {
      -      "description": "USD loaded onto the card balance.",
      -      "type": [
      -        "number",
      -        "null"
      -      ]
      -    },
      -    "network": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "note": {
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "payment_network": {
      -      "description": "The chain the payment settled on: `solana` (bridged to Base over CCTP) or `base` (forwarded directly).",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "status": {
      -      "description": "Always `paid` here: the payment settled and delivery to the card balance has started. Follow the later states in `GET /list-card-transactions`.",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "top_up_id": {
      -      "description": "Identifies this top-up under `top_ups` in `GET /list-card-transactions`.",
      -      "type": [
      -        "string",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  4. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations flag a destructive, non-idempotent, open-world write, and the description adds genuinely useful traits beyond them: exact pricing with no markup, CCTP bridging from Solana/Base, the paid→bridging→delivered→credited status lifecycle, delivery timing under a minute, and explicit failure semantics ('nothing is stranded', funds credit the Laso balance). This is well beyond annotation coverage.

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 one-line purpose and uses bold section headers (Why/Price/requirement/Delivery/Follow/Recovery) so an agent can skim. It is on the long side and could trim some narrative detail, but nearly every section carries actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a money-moving tool with an output schema already present, the description covers the remaining agent-facing gaps: prerequisites, payment routing across two chains, timing, status tracking endpoints, and failure recovery. Nothing an agent needs to invoke it correctly is missing.

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 amount bounds, so the baseline is 3; the description adds meaningful semantics the schema does not — the x402 price equals the amount, the exact amount is credited, and Laso absorbs the bridge cost. That additional pricing meaning justifies a 4.

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 precise verb+resource — loading the account holder's reloadable card balance at the card issuer — and immediately scopes it against siblings by naming create_reloadable_card as the follow-up and push/create-card tools as distinct steps. An agent can tell this apart from other funding tools without opening a schema.

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 strong context: a linked card issuer account is required, the agent wallet must exist and be funded first (get_agent_wallet), this should be followed by create_reloadable_card, and failures can be retried or recovered with withdraw. It lacks an explicit 'when-not to use this vs. a sibling' exclusion, which keeps it just short of a 5.

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