Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

create_reloadable_card

Create a reloadable card

Creates a reloadable card funded from the account holder's balance with the card issuer, and returns it. This is the same card the holder creates in the Laso dashboard, so an agent and a human end up with the same product.

The card is reusable by default (reusable: true): it stays open across charges until its limit is spent. Pass reusable: false for a single-use card that closes after its first approved charge.

This route is free — no x402 payment. The card draws on the account holder's own balance with the issuer, so Laso fronts nothing.

If the balance is short, this route answers 402. Fund it by sending USDC: GET /get-card-deposit-address returns the holder's own deposit address at the card issuer (USDC on Base only), and the balance credits within a couple of minutes. The holder can also top up with Apple or Google Pay in the dashboard.

Read the new card's number and CVV with /get-card-data?card_id=.... A card created here is Laso-issued, so its card_details come back directly — the approval step applies only to cards the holder created in a different app.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reusableNoWhether the card stays open across charges. Defaults to `true`; `false` closes it after the first approved charge.
auth_tokenNoLaso credential. Only if the MCP connection has no Authorization header.
usd_amountYesAmount in US dollars to load onto the card, minimum $1. Sent as dollars, not cents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "card": {
-      "properties": {
-        "balance": {
-          "description": "Card balance in US dollars.",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "card_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "card_type": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "expiry": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "last4": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "reusable": {
-          "type": [
-            "boolean",
-            "null"
-          ]
-        },
-        "spend_limit": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It thoroughly explains the card's reusability, the funding source, the free nature, the 402 error condition, the deposit address retrieval, and the direct availability of card_details for Laso-issued cards. This is comprehensive and exceeds what annotations would typically provide.

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?

The description is well-structured with clear paragraphs and bold key terms. It front-loads the main purpose and then covers reusability, cost, error handling, and follow-up actions. While it is somewhat long, each sentence contributes meaningful information, and the structure aids comprehension.

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?

The description is complete for a tool with no output schema. It explains what the tool returns ('returns it'), how to access card data via /get-card-data, and the distinction from other card creation routes. It also covers edge cases like insufficient balance and funding methods, ensuring an agent has all necessary information to call the tool correctly.

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%, so the baseline is 3. The description adds extra meaning beyond the schema: it clarifies 'usd_amount' is in dollars (not cents) and has a $1 minimum, and elaborates on 'reusable' with the behavior of staying open until limit is spent. This adds value beyond the schema definitions.

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?

The description clearly states the verb and resource: 'Create a reloadable card' and explains it is funded from the account holder's balance and returns the card. It distinguishes from sibling tools by noting it is the same card created in the Laso dashboard and contrasts with cards from other apps that require approval. This makes the tool's purpose unambiguous.

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?

The description provides clear context on when to use this tool: it creates a reloadable card, is free (no x402 payment), and is Laso-issued so no approval step is needed. It also explains the error case (402 when balance is short) and how to fund the card. While it doesn't explicitly name alternative tools to avoid, the context effectively guides usage.

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

All Laso Finance toolsInspect
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