Skip to main content
Glama

Create a cart

create_cart

Start the open UCP purchase flow, no auth needed. Creates a cart session and returns a cart_id (24-hour TTL). Optionally seed with pre-configured blind items and customer details. Next step: update_cart to add items, then create_checkout → complete_checkout to mint the payment link. Duo Roller: colour is one blockout and one sheer written "Blockout + Sheer" (get_product returns duo_fabrics).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_cart"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoOptional configured items; all submitted prices are ignored
customerNo

Output Schema

NameRequiredDescriptionDefault
itemsYes
cart_idYes
currencyYes
customerYes
total_zarYes
created_atYes
expires_atYes
item_countYes
updated_atYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only declare a non-destructive, closed-world write; the description adds genuinely new behavior: no authentication, a 24-hour TTL on the cart session, and that seeding with items/customer is optional. It does not say what happens to an existing open cart or whether cart creation is idempotent, which is the main remaining gap.

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-loads the core action and return value in the first two sentences, then compacts the workflow into an arrow chain. The closing Duo Roller sentence is relevant domain guidance but arrives without any framing, so it reads as a non-sequitur in an otherwise tight definition.

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?

Covers the entry-point role, auth requirement, session lifetime, optional seeding, and downstream tool sequence, and a rich output schema exists so return-shape detail is unnecessary. Nothing an agent needs in order to call this correctly on the first attempt 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?

Adds meaning beyond the schema by framing items as "pre-configured" (implying configure_product should run first) and reiterating that submitted prices are ignored and customer details are checked later. The Duo Roller colour rule injects domain semantics the schema does not carry, though the meaning of the two top-level parameters is mostly left to the detailed nested 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?

A specific verb plus resource ("Creates a cart session") with the concrete return value and lifetime ("returns a cart_id (24-hour TTL)"). It also frames the tool as the entry point of the UCP purchase flow, which no sibling provides.

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 precondition ("no auth needed") and routes the agent through the workflow: "Next step: update_cart to add items, then create_checkout → complete_checkout to mint the payment link." That names both the immediate next tool and the terminal one, so the agent need not guess sequencing.

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