Skip to main content
Glama

Laso Finance

by finance.laso
OverviewDiscussionsAdmin

order_gift_card

Order a gift card

Pay USDC via x402 to order a gift card. First browse the catalog via GET /search-gift-cards to find the laso_server_id for the card you want, then call this endpoint with the amount and product ID.

Pricing: amount is the card's face value in the product's own currency, not USD. Laso converts it to USD at the current exchange rate and adds the product's fee (up to 4.8%); that total is the x402 USDC price. A 100 SAR card costs roughly $28 USDC, not $100. Check the product's currency field in GET /search-gift-cards to see what amount is denominated in.

The $5 minimum and $9,000 maximum apply to the converted USD value, not the raw amount, so a foreign-currency amount is accepted only when its USD equivalent falls inside that range.

Returns redemption details (URL, code, and/or PIN) depending on the gift card brand.

PAID ROUTE (5-9432 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
amountYesGift card face value in the product's own currency (see the product's `currency` field in `GET /search-gift-cards`), not USD. The x402 price is this value converted to USD plus the product fee. After conversion it must be worth at least $5 and at most $9,000 USD.
countryNoISO 3166-1 alpha-2 country code (defaults to "US")US
auth_tokenNoLaso credential. Only if the MCP connection has no Authorization header.
laso_server_idYesThe product identifier from the gift card catalog (GET /search-gift-cards). Always copy it from a search result; an id that is not in the catalog returns 404 `unknown_laso_server_id`. Amazon is `amazon` for every country, selected with `country`.

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"
-      ]
-    },
-    "gift_card": {
-      "description": "Gift card order result with redemption details.",
-      "properties": {
-        "amount": {
-          "description": "Gift card face value, denominated in the product's own `currency` (not USD)",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "card_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "country": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "currency": {
-          "description": "ISO 4217 code the `amount` is denominated in, e.g. `USD`, `SAR`, `EUR`",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "laso_server_id": {
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "pin_code": {
-          "description": "PIN code for the gift card (if applicable)",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "redemption_code": {
-          "description": "Code to redeem the gift card (if applicable)",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "redemption_url": {
-          "description": "URL to redeem the gift card (if applicable)",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "status": {
-          "description": "One of: completed.",
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "timestamp": {
-          "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 fully carries the behavioral burden. It discloses the material financial behavior: amount is not USD, conversion and fee calculation, the 5–9000 USD minimum/maximum applied to converted value, automatic payment from the agent wallet, and the return shape. This is unusually transparent for a paid action.

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 clear bold labels and front-loaded operational steps. Every section earns its place: workflow, pricing, limits, return behavior, and payment route. Despite its length, it avoids fluff and is easy to parse.

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 tool's complexity, the absence of an output schema, and no annotations, the description is remarkably complete. It covers prerequisites, pricing, currency semantics, constraints, return content, and the funding requirement. There is no output schema, but the description compensates by naming the expected redemption 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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful behavior beyond the schema by explaining the conversion and fee mechanics with a concrete example (100 SAR ≈ $28 USDC) and reinforcing that the USD limits apply post-conversion. This adds real value to the agent's understanding of both amount and laso_server_id.

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 states a specific action ('Order a gift card') and clearly differentiates it from related sibling tools like order_intl_card by focusing on gift cards, catalog search, and x402 payment. It also specifies the exact workflow and what the call returns, leaving no ambiguity about the tool's purpose.

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 strong usage context: first browse GET /search-gift-cards, then call with amount and product ID, and ensure the managed agent wallet exists and is funded. It does not explicitly name or exclude alternative payment/order tools, but the catalog-first workflow and wallet prerequisite give clear actionable when-to-use guidance.

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