Skip to main content
Glama

Open a booking hold

booking_intent

WHAT BECOMES OF THE MONEY: it sits in an on-chain escrow that stays the buyer's. On a booking the wallet that funds the deposit is the wallet that confirms it — one signature on the booking page, no code needed — and the shop's no-show terms, which the buyer accepted before paying, can pay the deposit to the shop after the appointment. 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. A hold nobody acts on stays locked when its window closes; each checkout hold also carries a pre-signed return that pays only the wallet the hold was opened for, and sending it automatically at expiry, and handing it to the buyer, is being built. 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. IF THE APPOINTMENT IS CANCELLED, the shop's own cancellation terms decide, and they were SEALED onto this hold when it opened: the free-cancel window, what a late cancel or a no-show keeps, and a dispute window (72 hours on the standard terms). The arbiter enforces the copy recorded at open, not a later opinion. Read the shop's OWN terms back to your human rather than describing a default — ask the shop, never assume. Open a reversible DEPOSIT hold on a real appointment, in your human's name. Same ceiling as checkout_intent and the same reason: this is a HOLD, not a booking that has taken money. A booking's backup code goes to the buyer's own inbox, never to you, and on a checkout the code that completes the order lands there too; an unfunded hold hands the slot back on its own. FUND IT YOURSELF when buyer_wallet is your own purse — the human should be confirming a deposit that is already sitting in escrow, not sending one. Hand the funding transaction over only when the wallet is theirs. You must pass the buyer's real email and Stellar public key, and the shop's cancellation policy is consented to by asking for this.

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>",
      "service": "<service>",
      "starts_at": "<starts_at>",
      "buyer_name": "<buyer_name>",
      "buyer_email": "<buyer_email>",
      "buyer_wallet": "<buyer_wallet>"
    },
    "name": "booking_intent"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoanything the shop should know
shopYesthe shop's slug
becauseNothe brief-line that drove this booking — it rides the buyer's mail
serviceYesthe service id from booking_offer
starts_atYesthe opening you want, ISO — from booking_offer's list
buyer_nameYeswho the appointment is for
buyer_emailYesthe buyer's real inbox — a booking's backup code goes there, and on a checkout the code that completes the order does too
buyer_walletYesthe wallet this deposit 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. Changed1 schema field changed
    • changedInput schema / properties / buyer_email / description
      Previous value: -"the buyer's real inbox — the release code lands there, not here"New value: +"the buyer's real inbox — a booking's backup code goes there, and on a checkout the code that completes the order does too"
  2. First observed

TDQS

A3.5/5.0
Behavior5/5

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

Annotations only declare readOnly=false, destructive=false, openWorld=true and idempotent=false. The description adds substantial non-obvious behavior: funds sit in an escrow that remains the buyer's, a 2% fee is taken inside the completing transaction but not on unwinds, a goods hold defaults to a 70-minute window while appointment windows come from shop terms, holds lock at expiry with nobody acting, backup codes go only to the buyer's inbox, and cancellation terms are sealed at open and enforced as sealed. None of that is recoverable from the annotations or schema, and nothing contradicts them.

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 a dense wall of all-caps fragments mixing current behavior, legal framing and features described as still "being built," with the operative instruction (open a deposit hold) placed after the finance lecture. Every sentence may be individually true, but the ordering is inverted and the reader must reconstruct the core action from scattered clauses.

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

Completeness3/5

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

For an 8-parameter, 6-required, non-idempotent mutation with no output schema, the money flow, fee, expiry and refund routing are covered well, and the funding split between agent-held and buyer-held wallets is addressed. What is missing is a clear statement of what the agent gets back from a successful call (a hold reference? a funding transaction to pass along?) and how this tool relates to booking_offer as its prerequisite.

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 field descriptions already carry the basics and the baseline is 3. The prose adds meaning on top: `buyer_wallet` determines who must fund the deposit and therefore the calling workflow, `because` rides the buyer's mail, and asking for the booking is itself the act of consenting to the shop's cancellation policy. That is genuine semantic coupling rather than restatement.

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

Purpose3/5

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

The actual purpose is stated specifically but buried roughly two-thirds of the way in: "Open a reversible DEPOSIT hold on a real appointment, in your human's name." Before that, the reader wades through escrow mechanics, expiry windows and fee mechanics, so an agent skimming cannot tell what the tool does from the opening lines. The only sibling differentiation is an oblique "Same ceiling as checkout_intent," which does not state which one to use for which situation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is real conditional guidance inside the text: "FUND IT YOURSELF when `buyer_wallet` is your own purse" versus "Hand the funding transaction over only when the wallet is theirs," and "Read the shop's OWN terms back to your human ... ask the shop, never assume." However, there is no statement of when this tool should be chosen over checkout_intent or booking_offer, so tool-level routing is left to inference.

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