Skip to main content
Glama

Loyaltie

Build cart link

build_cart_link
Idempotent

A loyaltie.com cart link for 1 to 20 listed products (quantity 1 to 99, each id once, one-time purchase). It places no order and takes no payment: give the link to the person; they review the cart on loyaltie.com and, to pay, sign in or create an account there; tell them that. 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. It checks only that each product is listed, not that it is in stock; sold-out products are left out when the person opens the link, which sets each linked product's quantity to the link's (it is not added on top) and keeps other products already in the cart. You never pay or place an order. Unknown ids fail with not_found.

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": "build_cart_link"
  }
}

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 link to build: line_items, with optional context and attribution.
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

A3.7/5.0
Behavior3/5

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

The annotations already declare idempotentHint=true and destructiveHint=false, and the description corroborates this with 'sets each linked product's quantity to the link's (it is not added on top) and keeps other products already in the cart'. It also adds genuinely new behavior: no order or payment is placed, sold-out products are silently dropped, and unknown ids return not_found. This is solid added context, though the safety profile is largely carried by the annotations.

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 core artifact is front-loaded, but the paragraph is long and comma-spliced, and the no-order/no-payment promise is stated twice ('It places no order and takes no payment' and 'You never pay or place an order'), which is redundant. Most remaining sentences do carry non-obvious edge-case value.

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, so return values need no explanation, and the description still covers the error path (not_found), the sold-out edge case, cart-merge semantics, and the human follow-up flow. For a tool with nested objects and four parameters, nothing an agent needs to call it correctly is missing.

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?

Schema description coverage is 100%, so src, cart.line_items, context, attribution, meta and agent_id are all already documented, which sets the baseline at 3. The description restates quantity and id-uniqueness rules that the schema already covers, and contributes little parameter-level meaning beyond the link-open quantity-override behavior.

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?

The description states a specific artifact (a loyaltie.com cart link) with explicit scope (1 to 20 listed products, quantity 1-99, one-time purchase), so an agent knows exactly what is produced. It never names the sibling create_cart, which is the most plausible point of confusion, so differentiation is implied by 'places no order' rather than stated.

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?

It gives clear operational guidance for the agent's next step: hand the link to the person, tell them they sign in or create an account on loyaltie.com to pay, and ask them to check the total. What is missing is an explicit statement of when to choose this over create_cart or get_cart.

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