Skip to main content
Glama

withdraw_card_balance

Destructive

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.

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>",
      "destination_address": "<destination_address>"
    },
    "name": "withdraw_card_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesUSD to withdraw from the card balance (min $2, max $10,000).
destination_addressYesThe 0x-prefixed Base wallet address that receives the USDC. Must be one you control; Base only.

Output Schema

NameRequiredDescriptionDefault
noteNoTiming and where to see the request afterwards.
assetNo
amountNoUSD the issuer will pay out.
statusNoAlways `requested`: the issuer has accepted the request and will pay it out manually.
networkNo
withdrawal_idNoThe card issuer's reference for this payout request. Quote it to support; it also appears on the matching `withdrawal` card event.
destination_addressNoThe Base address the USDC goes to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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": {
      +    "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"
      +}
  2. Changed1 schema field changed
    • 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
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark destructiveHint=true and idempotentHint=false, and the description adds substantial behavioral context beyond that: payouts are manual and take 1-3 business days, there is no status route to poll, the request is recorded as a withdrawal event, and pending withdrawals count against the balance. No contradiction with annotations.

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 bolded section headers and no filler; every paragraph serves a concrete purpose. It is slightly longer than strictly necessary and repeats a few schema-covered facts such as the amount range and Base-only requirement, but that redundancy is defensible for a destructive financial operation.

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 high-stakes, externally-settled mutation, the description covers prerequisites, destination constraints, timing, ledger visibility, and balance semantics. Since an output schema exists, not describing the response shape in prose is acceptable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds meaning beyond the schema: the amount is bounded by the issuer-releasable balance including pending withdrawals, and the destination must be a Base wallet you control, explicitly excluding Solana agent wallets and the card deposit address.

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?

Opens with a specific verb+resource: 'Withdraw from a reloadable card balance' and immediately defines the operation as moving unspent money off the card via the issuer paying USDC on Base. It is explicitly contrasted with GET /fund-card-balance, making the tool's purpose distinguishable from a key sibling.

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 clear when-to-use and when-not-to-use conditions: Base only; a Solana agent wallet cannot receive this; the card deposit address is not a valid destination. It also names the reverse operation, fund-card-balance, and gives a prerequisite: a linked card issuer account is required.

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