Skip to main content
Glama

Open a purchase hold

checkout_intent

WHAT BECOMES OF THE MONEY, so you can tell your human before they agree: it sits in an on-chain escrow that stays THEIRS, and it reaches the shop only when the buyer themselves acts on the link in their own mail — a hold takes two of three keys, the buyer's, the shop's and ours, so one key alone moves nothing. The link that finishes it goes to the buyer's own mail, never to you. A goods hold's window is 70 minutes by default — a 60-minute reap window plus ten minutes of grace; an appointment deposit's window comes from the shop's own terms. If nobody acts before the window closes, the money stays locked in the hold and on a checkout the buyer can take it back with their emailed link while our service is up. Each hold also carries a pre-signed return that pays only the wallet the hold was opened for; sending it automatically at expiry is being built. One never funded simply lapses. The platform's 2% escrow fee sits inside the same on-chain transaction that completes the order; an unwind back to the buyer carries none. Every hold gets its own fresh on-chain address. Where a shop divides a sale between people, those shares and addresses are SEALED when the hold opens and cannot be amended afterwards. Open a REVERSIBLE escrow hold on goods for the person you shop for. This is not a purchase: the money stays the buyer's until THEY act — the code that completes the order goes to the BUYER's email (never to you); an unfunded hold simply lapses, and on a checkout a hold nobody confirms stays locked for the buyer to take back with their emailed link while our service is up. FUND IT YOURSELF when buyer_wallet is your own PURSE. You get back the order reference, the escrow address, the amount and a funding transaction, and paying it is YOUR job: then your human's only act is confirming or refusing from the mail — the money is already in escrow and they never touch a wallet. That is what the hold is for. A purse can only ever move money into a place a human decides, so funding a hold is not spending, which is why holding money is safe for you and not for a push payment. If a mandate covers your purse its per-order and per-period ceilings are checked BEFORE anything opens, and a refusal costs nothing. Hand the funding transaction over ONLY when the wallet is your human's own. Anything PHYSICAL needs a rate_token from shipping_options first — the hold is struck at an exact amount and cannot be topped up, so the postage has to be inside it. Use concierge_ask first to know stock and fit; quote prices honestly from what this returns.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "shop": "<shop>",
      "items": "<items>",
      "buyer_email": "<buyer_email>",
      "buyer_wallet": "<buyer_wallet>"
    },
    "name": "checkout_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
shopYesthe shop's slug
itemsYeswhat to hold — listing ids from the shop's public shelf (concierge_ask's live.goods rows carry them)
becauseNoone plain sentence naming the brief-line that drove this buy (e.g. 'within the tees ceiling of $40.00') — it rides the order email so your human reads WHY, in their own document's words
ship_toNoshipping address, REQUIRED for anything physical — pass it as an object, not as text
fund_assetNowhat the funding wallet SPENDS: 'xlm' (default), 'usdc' or 'eurc' — the hold itself is always denominated in XLM; a non-XLM choice funds it by path payment from that asset
rate_tokenNothe shipping token from shipping_options, for the service you picked. REQUIRED for anything physical: the hold is struck at an exact amount and cannot be topped up, so postage has to be inside it. It is bound to the address you priced against — pass the same `ship_to` object back.
buyer_emailYesthe buyer's REAL email — the release code lands there, and without it the order can never settle
buyer_walletYesthe wallet this hold REFUNDS to (G + 55 base32) — your own purse when you hold one, and then you fund it yourself; otherwise the buyer's own key

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Far beyond the annotations, it discloses escrow key structure, the 70-minute goods window versus shop-defined appointment windows, the 2% fee inside the completing transaction, that expediting shares are sealed and unamendable, and that a pre-signed return currently is not auto-sent. This is unusually rich behavioral detail for an openWorld non-destructive mutation, though the account is stated in dense, digressive prose rather than a clean profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded on the money question, which is the right lead, but the body is heavily repetitive: "an unfunded hold simply lapses" appears twice, and the buyer-email-only release is restated three times. All-caps emphasis and stacked clauses make it slow to parse for an agent that mainly needs the call contract.

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 an eight-parameter tool with no output schema, it covers the return values (order reference, escrow address, amount, funding transaction), the funding obligation, expiry behavior, fee incidence, and physical-goods prerequisites. Nothing needed to call it correctly or to explain the outcome to a human appears to be 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 already 100%, so the baseline is 3; the description still adds meaning by clarifying the purse-versus-buyer-wallet decision and the funding obligation that follows, and by tying rate_token to the non-toppable exact amount. It does not add much on shop/items/because beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Open a REVERSIBLE escrow hold on goods" gives a specific verb and resource, and the definition explicitly contrasts it with a purchase ("This is not a purchase") and with push payments. It also hints at the goods-vs-appointment split ("on goods", "an appointment deposit's window”) without naming booking_intent, so the sibling boundary is implied rather than stated.

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 explicit sequencing and prerequisites: call concierge_ask first for stock and fit, get a rate_token from shipping_options before anything physical, and refuse to hand over the funding transaction unless the wallet is the human's own. It also states the self-funding condition when buyer_wallet is your own purse, and that mandate ceilings are checked before anything opens with a refusal costing nothing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources