Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

get_card

Order a USA prepaid card

Pay between $5–$1000 USDC to order a Laso Finance USA prepaid card. By default returns JSON with auth credentials and card info (for AI agents). Pass format=html to get an HTML redirect to the card redemption URL (for browser-based flows).

The JSON response includes a card.status of "pending". Card details (number, CVV, etc.) take ~7-10 seconds to become available. Poll getCardData at the callableBaseUrl to check when status becomes "ready".

U.S. only. This card is issued in USD and can only be used for purchases at U.S.-based merchants. Physical goods must ship to a U.S. address. For non-U.S. merchants or non-USD currencies, use GET /order-intl-card instead. This endpoint is intended for the caller's own use — the card is non-transferable.

PAID ROUTE (5-1000 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountYesUSD amount to load on the card (min $5, max $1000)
formatNoResponse format. `json` (default) returns auth credentials and card info for agents. `html` returns a redirect page for browsers.json
auth_tokenNoLaso credential. Only if the MCP connection has no Authorization header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "auth": {
-      "properties": {
-        "expires_in": {
-          "description": "Token lifetime in seconds",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "id_token": {
-          "description": "ID token — use as Bearer token for Laso Finance APIs",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "refresh_token": {
-          "description": "Use with POST /auth (grant_type=refresh_token) to get a new id_token when it expires",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "callable_base_url": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "card": {
-      "description": "Card order info returned by /get-card. Status is always `pending` initially — poll `/get-card-data` to check when card details are ready.",
-      "properties": {
-        "card_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "country": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "description": "Always `pending` at order time. Poll `/get-card-data` to check for `ready`. One of: pending.",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "timestamp": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "timestamp_readable": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "usd_amount": {
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "user_id": {
-      "description": "The user's ID (lowercase wallet address)",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and excels. It discloses that this is a paid route (x402 USDC auto-payment from agent wallet), requires a funded wallet (references get_agent_wallet), returns a pending status, and that card details take 7-10 seconds to become available. It also notes the US-only restriction and non-transferability. No contradictions exist.

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?

The description is well-structured with bolded key sections (U.S. only, PAID ROUTE). It front-loads the core purpose and then logically expands to response handling, restrictions, and payment details. Each paragraph adds distinct value without redundancy, making it thorough yet organized.

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?

Given the complexity (payment, async status, geographic restrictions) and lack of output schema, the description covers all necessary aspects: payment flow, response format, polling instructions, alternatives, and prerequisites. It explains the return values (JSON with auth credentials and card info, pending status) and the callableBaseUrl for polling, making it complete for an agent to use correctly.

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 coverage is 100%, so baseline is 3. The description adds minimal extra meaning beyond the schema: it explains that format=html is for browser-based flows and that auth_token is only needed if no Authorization header, but these are already in the schema descriptions. The description does not add new parameter semantics beyond what the schema provides.

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 opens with a clear verb+resource: 'Order a USA prepaid card.' It specifies the payment method (USDC), the amount range, and the output format options. It distinguishes itself from siblings like order_intl_card and get_card_data by explicitly naming the alternative for non-U.S. use and the polling mechanism for card readiness.

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?

The description provides explicit when-to-use and when-not-to-use guidance: 'For non-U.S. merchants or non-USD currencies, use `GET /order-intl-card` instead.' It also instructs to poll getCardData after ordering, and warns that the card is non-transferable and intended for the caller's own use. This gives clear context and exclusions.

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