Skip to main content
Glama

taufnaus Geschenke-Shop

Bestellen

checkout

Create the order for a cart and return a payment_url (Stripe). The customer opens it, enters the delivery address and pays there (card, 3-D Secure). Nothing is charged before the customer confirms on that page. Ask the customer for their e-mail address first.

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": {
      "cart_id": "<cart_id>",
      "email": "<email>"
    },
    "name": "checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesCustomer e-mail for the order confirmation
phoneNoCustomer mobile number (DE/AT/CH), only needed for send_payment_link_by_sms / _by_whatsapp
cart_idYes
countryNoDelivery country, ISO code (default DE)
send_payment_link_by_smsNoOnly if the customer asked for it: also send the payment link by SMS to phone. Paying still happens on the payment page.
send_payment_link_by_emailNoOnly if the customer asked for it: also send the payment link to the e-mail address
send_payment_link_by_whatsappNoOnly if the customer asked for it: also send the payment link by WhatsApp to phone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-idempotent, open-world write; the description adds substantial context: the payment is hosted by Stripe, uses card with 3-D Secure, requires the customer to enter the delivery address there, and nothing is charged before confirmation. It leaves unaddressed what happens to the cart after checkout and whether a repeated call creates a second order, which matters given idempotentHint=false.

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?

Four short sentences, front-loaded with the action and return value, followed by the customer-facing flow and the no-charge guarantee. Every sentence carries information an agent would otherwise have to guess.

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

Completeness4/5

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

With no output schema, the description correctly takes on the burden of describing the single meaningful return value (payment_url) and the post-call flow. For a 7-parameter, non-idempotent, open-world write it is nearly complete, but it omits cart state after checkout and duplicate-order risk.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 86%, so the schema already explains email, phone, country, and the three optional send_payment_link_* flags. The description only reinforces that email must be collected before calling; it adds no format, default, or interaction detail beyond the schema, so the baseline 3 applies.

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 first sentence gives a specific verb and resource ("Create the order for a cart") plus the concrete return value (payment_url via Stripe). It is unmistakably distinct from siblings like get_cart, set_cart, and get_order_status, which read or mutate the cart or query status rather than finalize an order.

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?

It establishes the sequencing precondition ("Ask the customer for their e-mail address first") and makes clear the actual payment happens outside the tool, on the returned page. It does not explicitly state when not to use it (e.g., cart not finalized, repeat calls creating duplicate orders) or name an alternative, so it falls short of a 5.

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