Skip to main content
Glama

Start checkout

create_checkout
Destructive

Phase 1 of 2 in the purchase flow. Convert a cart (or inline items + customer) into a checkout. Customer name, email, and phone are required. Returns checkout_id. No payment link is minted yet, call complete_checkout for that. Use update_checkout to correct customer details before finalising.

Input Schema

NameRequiredDescriptionDefault
itemsNo
cart_idNoEither cart_id or items required
customerNo
payment_methodNoDefault 'yoco'

Output Schema

NameRequiredDescriptionDefault
ap2No
itemsNo
statusYes
messageNo
currencyYes
customerNo
next_stepNo
total_zarYes
item_countNo
checkout_idYes
payment_urlNo
payment_methodNo
provider_referenceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, and the description adds flow context the annotations cannot: this creates an intermediate object, not a payable one, and it is the prerequisite for complete_checkout. It also flags that customer details are validated ('required', with the schema noting they are 'checked before checkout creation'). It does not explain the destructive angle — whether a created checkout holds stock, expires, or must be cancelled via cancel_checkout — so it falls short of full behavioral disclosure for a mutation tool.

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 phase position and the core transformation, then the return value, then the routing to siblings. No filler or repeated schema content.

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?

An output schema exists, so return values need not be explained, and the flow positioning is complete for a 4-parameter nested-input mutation. The notable gap is the payment_method parameter and the expiry/cancellation lifecycle of a created checkout, which matter given destructiveHint=true.

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?

Coverage is 50%, and the description adds real meaning for the customer fields (name/email/phone required, though the schema's anyOf shows cart_id alone can suffice). It says nothing about payment_method, the cart_id vs items alternative, or the price-recalculation fields, leaving the low-coverage half to the schema alone.

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?

Names the specific transformation ('Convert a cart (or inline items + customer) into a checkout') and positions it as 'Phase 1 of 2 in the purchase flow', which immediately separates it from complete_checkout. An agent can identify verb, resource, and scope 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?

Explicitly states the boundary condition ('No payment link is minted yet, call complete_checkout for that') and names a second alternative ('Use update_checkout to correct customer details before finalising'). Both when-to-use and when-to-use-something-else are given.

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