Skip to main content
Glama
Sign In

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

order_intl_card

Destructive

Order an international prepaid card

Order an international non-reloadable prepaid card (USD). Not for merchants that bill later. Ad platforms (Google, Meta, Reddit and the like), AI and inference providers, subscriptions, and any merchant that keeps a card on file and charges it after use need the reloadable card (POST /create-reloadable-card). This card has a fixed balance and cannot be topped up, so those merchants decline it or fail the later charges. Ask what the card is for before ordering one.

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, or a lower rate while a limited-time fee promotion is running (it can be 0%). The 402 challenge always carries the exact total. Minimum $100, maximum $1,000 on-card amount. The $1,000 maximum is the amount loaded on the card and does not change with the fee rate. 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 (100-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

NameRequiredDescriptionDefault
amountYesOn-card USD amount (min $100, max $1,000 regardless of the fee rate). Must be a whole dollar amount: the issuer only issues whole-dollar cards. The x402 payment is this amount plus a 3.8% fee, or less during a fee promotion.

Output Schema

NameRequiredDescriptionDefault
authNo
messageNo
user_idNo
intl_card_orderNo
callable_base_urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / intl_card_order / properties / card_id
      Added value: +{
+  "description": "Id of the queued order. Pass it as `card_id` to `GET /get-card-data` to poll for the card details, or to `POST /cancel-intl-order` while the order is still queued.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / amount / description
      Previous value: -"On-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."New value: +"On-card USD amount (min $100, max $1,000 regardless of the fee rate). Must be a whole dollar amount: the issuer only issues whole-dollar cards. The x402 payment is this amount plus a 3.8% fee, or less during a fee promotion."
  3. 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": {
+    "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"
+}
  4. 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
  5. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare the mutable/destructive profile, but the description adds a lot beyond them: the order is queued and admin-fulfilled, card details only appear afterward via `GET /get-card-data` with a specific card_type, a 3.8% fee (or promotional rate, possibly 0%) applies, the 402 challenge carries the exact total, and placing the order accepts three named legal agreements. That is the kind of consequence disclosure an agent needs before a destructive, non-idempotent purchase.

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?

It is front-loaded with the one-line purpose and the decisive "not for" warning before any fee or legal detail, so an agent can triage quickly. It is on the long side, and the three inline legal URLs plus the repeated fee/min-max restatement edge toward redundancy, but no sentence is purely 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?

For a one-parameter, destructive, real-money purchase tool, the description covers prerequisites (funded managed wallet), cost mechanics, fulfillment latency, follow-up retrieval, cancellation, and consent. An output schema exists, so the absence of return-value detail is appropriate, and nothing needed to call this 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%, so baseline is 3, but the description adds real meaning: the on-card amount is separate from the fee, the $1,000 cap applies to the loaded amount regardless of fee rate, amounts must be whole dollars, and the total paid ranges roughly 100–1038 USD. It reinforces the min/max rather than extending it, which keeps it just short of a 5.

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 opening sentence states a specific verb and resource: "Order an international non-reloadable prepaid card (USD)." The word "non-reloadable" immediately separates it from the sibling create_reloadable_card, and the sibling inventory also contains order_card and order_gift_card, so the qualifier does real disambiguating work.

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?

It gives an explicit exclusion ("Not for merchants that bill later"), enumerates the affected merchant classes, and names the correct alternative (`POST /create-reloadable-card`) with the reason (declines/failed later charges). It also adds a pre-flight instruction ("Ask what the card is for before ordering one"), a cancellation route via cancel_intl_order, and a funding prerequisite via get_agent_wallet.

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