glasstopfen.de

Create checkout

create_checkout

Create a checkout session (UCP checkout). Nothing is charged; the response lists totals, missing buyer inputs and payment handlers. Shipping address in checkout.fulfillment.methods[0].destinations[0] (address_country decides price and currency), email in checkout.buyer.email. Custom-made items: line_items[].custom_inputs = {vehicle:{make,model,year}, measurements:{opening}}. Limits: at most 3 per line item and 5 items per checkout (otherwise quantity_limit_exceeded, nothing is created).

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>"
    },
    "name": "create_checkout"
  }
}

Input Schema

Name	Required	Description	Default
`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.7/5.0

Behavior5/5

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

Beyond the annotations (which only declare this is a non-destructive, non-idempotent write), the description discloses the key non-obvious behavior: no charge is incurred, the response enumerates totals/missing inputs/payment handlers, and exceeding the 3-per-line-item or 5-item limits returns quantity_limit_exceeded with nothing created. The side-effect profile is stated precisely and consistently with destructiveHint=false and readOnlyHint=false.

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?

Purpose and the no-charge caveat are front-loaded, followed by parameter mapping and then limits, so the agent gets the essentials first. It is dense with parenthetical path expressions and could be broken into shorter sentences, but no sentence is filler.

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?

Given an output schema exists, the definition is not obligated to explain return values, and it still summarizes the useful ones. Combined with the placement of required nested inputs and the failure limits, an agent has everything needed to call this correctly on the first attempt.

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

Parameters5/5

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

Schema coverage is already 100%, yet the checkout object is only documented as "shape per" an external URL, so the description earns real credit by mapping concrete nested paths: fulfillment.methods[0].destinations[0], buyer.email, and the custom_inputs object shape for made-to-order items. It also explains that address_country drives price and currency, which is semantic meaning absent from 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?

The definition opens with a specific verb and resource ("Create a checkout session (UCP checkout)") and immediately clarifies the scope boundary with "Nothing is charged," which distinguishes it from the payment/order-completion siblings. An agent knows exactly what this call produces 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 Guidelines4/5

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

The statement that nothing is charged and that the response reports missing buyer inputs and payment handlers implies the pre-payment step of the flow, giving clear usage context. However, it never names an alternative such as complete_checkout or the cart-update siblings, so the agent must infer the rest of the flow rather than being routed to it.

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?