glasstopfen.de

Complete checkout

complete_checkout

Idempotent

Place the order with checkout.payment (instruments[].handler_id from the business profile, e.g. bank_transfer). Only call after the buyer approved the total. meta.idempotency-key is required. The result carries order.id and a one-time order.order_token for get_order. Card, if listed in the profile (any currency): handler_id card_payment_page answers status requires_escalation with continue_url = Stripe-hosted payment page (de.glasstopfen.payment_page); hand the link to the buyer, nothing is placed until Stripe confirms, then get_checkout shows status completed with the order. handler_id stripe_payments takes instruments[].credential = {type: stripe_payment_token, token: spt_...}. Bank transfer (EUR orders only; other currencies get bank_transfer_eur_only and nothing is placed): the order is on hold and the result contains de.glasstopfen.payment_instructions (account_holder, iban, bic, bank_name, amount, currency, reference = order number, payment_due, payment_deadline = transfer deadline, currently 7 days, after it the order is cancelled automatically); show these exact values to the buyer. The destination is fixed by create/update_checkout (countries without delivery: country_not_supported); complete_checkout never changes it: the same destination may be resent, a different one answers destination_change_not_allowed and nothing is placed. Placing the order concludes a binding contract (terms: /legal/agb, withdrawal: /legal/widerruf).

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": {
      "checkout": "<checkout>",
      "id": "<id>"
    },
    "name": "complete_checkout"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Resource id.
`meta`	No	UCP request metadata: {"ucp-agent": {"profile": "<platform profile URL>"}, "idempotency-key": "<uuid>"}.
`checkout`	Yes	UCP checkout payload, shape per https://ucp.dev/2026-08-25/schemas/shopping/checkout.json

Output Schema

Name	Required	Description	Default
`ucp`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the description's credit is for context beyond that: the binding-contract consequence, the 7-day bank-transfer deadline with automatic cancellation, the hold semantics, and the Stripe-confirmation side path. However, the sentence structure is so compressed that these traits are buried in parentheticals rather than surfaced as distinct behaviors, which weakens the disclosure despite the rich content.

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

Conciseness3/5

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

The essential constraints are front-loaded (place order, approval prerequisite, idempotency key), which is good. But several sentences are extremely long and pile parentheticals, example values, and error codes into single clauses, so the payment-handler variants read as a wall of text rather than a scannable structure.

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?

An output schema exists, yet the description still explains the salient returns (order.id, one-time order.order_token, payment_instructions fields, named error codes), so nothing an agent needs to call or interpret the result is missing. Coverage is complete for a nested-payload, multi-branch payment tool.

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, and the description adds real meaning: it maps checkout.payment.instruments[].handler_id to concrete values (bank_transfer, card_payment_page, stripe_payments) and specifies the credential shape for stripe_payments (type stripe_payment_token, token spt_...). It also states that meta.idempotency-key is mandatory, which the schema lists only as an optional-looking nested property.

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 opening clause states a specific verb and resource ("Place the order with checkout.payment") and names the exact field that carries the payment method (instruments[].handler_id). This clearly separates it from read-side siblings like get_checkout and mutation siblings like update_checkout, so an agent can select it without opening the schema.

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?

Explicit prerequisites are given ("Only call after the buyer approved the total"), along with required metadata ("meta.idempotency-key is required") and follow-up routing ("then get_checkout shows status completed with the order", order_token for get_order). It also states when the call does NOT place an order (requires_escalation, bank_transfer_eur_only, destination_change_not_allowed), which is explicit when-not guidance rarely present at this level.

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

All glasstopfen.de tools Inspect

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

Need Help?