Skip to main content
Glama

Loyaltie

Create cart

create_cart

Create a cart on loyaltie.com for 1 to 20 listed products from any number of makers (quantity 1 to 99, each id once, one-time purchase). Prices and stock come from our catalog, never from the request. Returns id, line items with prices, totals for the items only (shipping, any discount and any Loyaltie+ membership in the cart are added at checkout), continue_url and expires_at: give the person continue_url; they sign in or create an account at checkout and pay on loyaltie.com, because paying needs an account. Ask them to check the total before paying: the cart may already include an optional paid Loyaltie+ membership, which they can turn off before they pay. You never pay or place an order. An unavailable or sold-out item fails the call with its path; a quantity above the stock on hand is lowered, with a warning.

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

Input Schema

NameRequiredDescriptionDefault
srcNoSend "skill" when you were set up by the Loyaltie Skill; returned links then carry src=skill. Default "api"; any other value counts as "api".
cartYesThe cart to create: line_items, with optional context, attribution and why.
metaNoOptional UCP request metadata. meta["ucp-agent"].profile is your UCP agent profile URL; it is recorded, never required.
agent_idNoYour agent id. Every loyaltie.com link returned then carries agent=<agent_id>, so Loyaltie knows which agent helped.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Discloses behavior that goes well beyond the annotations: prices and stock always come from the catalog and never from the request, an unavailable or sold-out item fails the call with its path, and an over-stock quantity is silently lowered with a warning. It also warns that the cart may already contain an optional paid Loyaltie+ membership the person can disable before paying, which is exactly the side-effect detail the annotations (readOnly=false, destructive=false) do not convey.

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-loaded with purpose and constraints, then moves to returns, then the human handoff. Dense but nearly every clause carries actionable information. Small waste in restating schema bounds ('quantity 1 to 99', '1 to 20 listed products').

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 everything needed for a 4-parameter nested-object creation tool: what is created, what is returned, what the agent must hand off, what failure and quantity-clamping look like, and the account requirement. Return values are explained even though an output schema exists, which is a bonus rather than a gap.

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; the description earns above that by adding rules the schema does not encode, notably 'each id once' and 'one-time purchase', and by tying parameter-level failure semantics to item ids ('fails the call with its path'). Quantities and bounds it repeats from the schema, which is mild redundancy rather than added meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

A specific verb plus resource and scope: 'Create a cart on loyaltie.com for 1 to 20 listed products from any number of makers'. An agent can tell this is cart creation rather than retrieval or link building, though it never names the sibling tools (build_cart_link, get_cart) explicitly.

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?

Strong usage context: it states that the person receives continue_url, must sign in or create an account at checkout, and that the agent never pays or places an order. This implicitly routes agents away from checkout flows, but it never explicitly contrasts this tool with build_cart_link or explains when to use that alternative.

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