Laso Finance

withdraw_card_balance

Withdraw from a reloadable card balance

Move unspent money off the account holder's reloadable card. The balance behind a reloadable card is held by the card issuer, and this asks the issuer to pay amount of it out as USDC on Base to the destination_address you supply. It is the reverse of GET /fund-card-balance, and free: the money is the holder's own, and Laso moves nothing itself.

Base only. The issuer pays on Base and nowhere else, so the destination must be a Base wallet you control. A Laso managed agent wallet holds USDC on Solana and cannot receive this. The card deposit address from GET /get-card-deposit-address is not a valid destination either.

Not instant. The issuer processes payouts manually, usually within 1-3 business days, and emails the account holder when the payout is sent. The response carries the issuer's withdrawal_id; there is no status route to poll. The request is recorded as a withdrawal event under card_events in GET /list-card-transactions, and the balance from GET /get-card-deposit-address drops once it is paid.

Amount: $2 to $10,000, and no more than the balance the issuer can release. Withdrawals the issuer has not paid yet still count against the balance, so a second request can only take what remains.

Confirm the amount and destination with the account holder before calling this. A linked card issuer account is required; the holder sets it up at https://laso.finance/agent/dashboard/verified/card.

Input Schema

TableJSON Schema

Name	Required	Description
`amount`	Yes	USD to withdraw from the card balance (min $2, max $10,000).
`auth_token`	No	Laso credential. Only if the MCP connection has no Authorization header.
`destination_address`	Yes	The 0x-prefixed Base wallet address that receives the USDC. Must be one you control; Base only.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 26, 2026

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "amount": {
-      "description": "USD the issuer will pay out.",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "asset": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "destination_address": {
-      "description": "The Base address the USDC goes to.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "network": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "note": {
-      "description": "Timing and where to see the request afterwards.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "status": {
-      "description": "Always `requested`: the issuer has accepted the request and will pay it out manually.",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "withdrawal_id": {
-      "description": "The card issuer's reference for this payout request. Quote it to support; it also appears on the matching `withdrawal` card event.",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null

First observedSep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

With no annotations, description carries full burden. It discloses manual processing (1-3 days), no status route, response contains withdrawal_id, event recorded in card_events, balance drops after paid, amount limits, pending withdrawals count against balance, and requirement for linked issuer account. Highly transparent.

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?

Well-structured with bold headers (Base only, Not instant, Amount) and each sentence adds value. Though somewhat long, the detail is necessary for a complex financial operation; no filler.

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?

Comprehensive for a withdrawal tool with no output schema: covers limits, network, timing, prerequisites, response contents, and balance impact. Nothing an agent needs to call 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% with descriptions for amount and destination_address, but description adds extra meaning: pending withdrawals count against balance, second request only takes what remains, destination must be controlled Base wallet. These constraints go beyond schema.

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: withdraw from a reloadable card balance, moving unspent money as USDC on Base. Clearly distinguishes from fund_card_balance and other withdrawal tools by explaining it is the reverse and specifying the network.

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 specifies when to use (Base only, destination must be a Base wallet you control) and exclusions (Solana wallet, card deposit address). Also gives prerequisites (linked issuer account, confirm with holder) and contrasts with fund_card_balance.

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

All Laso Finance tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?