Skip to main content
Glama

Place an order

place_order
Destructive

Places a REAL order for physical macarons shipped to a real address, and returns a crypto deposit address to send funds to. Confirm the total, the delivery address and the allergen warning with the person you are acting for BEFORE calling this. Pass either images (nine URLs, simplest — the set is built for you) or the set_hash and add_to_cart_fields returned by a previous preview_set call. Returns an order id, a crypto deposit address and amount, and a status link that needs no account or password. The order only reaches the bakery after the payment confirms. A recipient phone number is REQUIRED - carriers need it to generate a label, so collect it before calling.

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": {
      "email": "<email>",
      "recipient": "<recipient>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional short message for the card in the box.
emailYesAn address a human actually reads.
imagesNoNine public https image URLs in grid order. Simplest route: the set is built and carted for you. Omit if passing set_hash + add_to_cart_fields instead.
set_hashNoFrom preview_set. Requires add_to_cart_fields too.
recipientYesWho receives the box, and where.
shipping_idNoOptional: force a specific shipping-method instance id. Normally omit.
pay_currencyNoCrypto ticker to pay in, e.g. "usdttrc20". Optional; a default is chosen.
max_total_usdNoOptional safety ceiling in USD. The shipping cost is only known once the order exists, so set this to the most your human agreed to pay. If the real total is higher, the order is still created but NO payment instruction is returned.
reorder_nonceNoSet this ONLY to deliberately place a second, separate order with identical details (same set, same recipient). Any distinct value works. Without it, an identical repeat is treated as a retry and returns the original order.
idempotency_keyNoOptional explicit key. If omitted, one is derived from the order details, so retrying the identical request is safe and will not create a duplicate.
confirm_total_usdNoConfirm a total your human has approved. Use this to RESUME an order that already exists: after an over-ceiling result, or when a repeat call matched an existing order and the payment instruction was withheld. Set it to the exact total shown. This never creates a second order - it returns the existing one WITH its payment instruction. This is the correct way to proceed; do NOT use reorder_nonce for this.
add_to_cart_fieldsNoThe `add_to_cart.fields` object exactly as returned by preview_set. Required when using set_hash instead of images.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations say destructive/open-world, but the description adds the critical consequences an agent needs: a real shipment to a real address, funds must be sent to a returned crypto address, and the order only reaches the bakery after payment confirms. It also discloses that the status link needs no account or password and that the carrier requires a phone number, none of which the annotations convey.

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?

Front-loaded with the highest-stakes fact (a real, paid, physical order) and the confirmation checklist, then the input routes and return values. Four dense sentences that mostly earn their place, though the closing phone-number sentence partially repeats what the schema already states in caps.

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 12-parameter, nested-object, high-stakes mutation with no output schema, the description supplies both the return shape (order id, deposit address and amount, status link) and the payment-gated fulfillment timing. Nothing an agent needs to call it safely and interpret the result 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 the baseline is 3; the description still adds a decision rule by calling the nine-URL `images` route 'simplest — the set is built for you' and by pairing it against the set_hash/add_to_cart_fields alternative. The phone-number requirement is re-emphasized but largely duplicates the schema.

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?

States a concrete verb and resource ('Places a REAL order for physical macarons shipped to a real address') plus the return payload (crypto deposit address, order id, status link). The 'REAL' emphasis and the reference to a previous preview_set call make it distinguishable from the sibling preview tool at a glance.

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?

Gives explicit preconditions — confirm total, delivery address and allergen warning before calling, and collect a recipient phone number first — plus two named input routes (images vs. set_hash/add_to_cart_fields from preview_set). It stops short of stating when not to use the tool at all (e.g., run preview_set or get_pricing first), so exclusions are only implicit.

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