Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

order_intl_card

Order an international prepaid card

Order an international non-reloadable prepaid card (USD). The order is queued and fulfilled by an admin — after fulfillment, card details become available via GET /get-card-data with card_type=Non-Reloadable International.

The x402 payment covers the on-card amount plus a 3.8% fee. Minimum $100, maximum $1,000 on-card amount. Submit a whole dollar amount.

Placing the order accepts the card issuer's terms on behalf of the account holder: the Cardholder Agreement, the E-Communications Disclosure, and the Privacy Notice.

If you need to cancel a queued order before it is fulfilled, use POST /cancel-intl-order.

PAID ROUTE (103.80-1038 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
amountYesOn-card USD amount (min $100, max $1,000). Must be a whole dollar amount: the issuer only issues whole-dollar cards. The x402 payment is this amount plus a 3.8% fee.
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"
-      ]
-    },
-    "intl_card_order": {
-      "properties": {
-        "charged_usd_amount": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "on_card_usd_amount": {
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "status": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "timestamp": {
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "message": {
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "user_id": {
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observed

TDQS

A4.5/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 disclosure burden, and it does so thoroughly. It discloses that the order is queued and fulfilled by an admin, that payment includes a 3.8% fee, that placing the order accepts legal terms, and that cancellation is possible before fulfillment. This is far more transparent than a generic 'order card' statement.

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 dense but organized into clear paragraphs covering fulfillment, fees, legal consent, cancellation, and payment. It loses one point because the opening sentence 'Order an international prepaid card' is redundant and less precise than the following sentence, which repeats and refines the same idea.

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

Completeness4/5

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

The description covers prerequisites, amount limits, fee structure, legal acceptance, cancellation, and the downstream data retrieval path, which is excellent for an asynchronous order tool. It does not specify the response shape or how an agent should poll for fulfillment, but it does point to get-card-data for accessing the final card details.

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?

The input schema already describes amount constraints and auth_token, so the baseline is 3, and the description adds real value by explaining the paid route, the automatic wallet payment, and the need to fund the wallet first. The auth_token parameter gains no new context, but the schema already covers it adequately.

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 names a specific resource type ('international non-reloadable prepaid card'), a concrete verb ('order'), and the currency. It distinguishes itself from siblings by explicitly saying 'non-reloadable' and by describing an admin-queued fulfillment flow that ends with data retrieval via get-card-data.

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 gives clear context for when this tool is appropriate: ordering a non-reloadable international USD card with specific amount constraints and a wallet-funding prerequisite. It explicitly routes to cancel_intl_order for cancellations and get_agent_wallet for wallet checks, but it does not explicitly explain when to prefer create_reloadable_card or order_gift_card instead.

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