Skip to main content
Glama

AIFEC

Server Details

Demo AI-first shop: search products, fill a cart and prepare the order (test payments).

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 18 tools

Disambiguation4/5

Most tools have clearly distinct resource+action targets, and the descriptions actively disambiguate the risky pairs (cart_add vs cart_update, checkout_review vs checkout_place). The main overlaps are shipping_quote vs checkout_shipping_options and check_availability vs get_product, where an agent could pick the wrong one, though the 'pre-cart quote' vs 'order-scoped' framing mostly resolves it.

Naming Consistency4/5

The set is organized by consistent domain prefixes (cart_*, checkout_*) with predictable suffixes, so grouping is easy to read. Minor deviation: some names are noun_verb (cart_add, checkout_place) while catalog tools use verb_noun (get_product, search_products, list_categories), so verb position is not uniform across the set.

Tool Count4/5

18 tools is slightly heavy but justified: the checkout flow genuinely decomposes into customer, shipping, payment, review, place, link and status steps. A few could arguably be merged (checkout_link into status, checkout_shipping_options into shipping_quote), but none feels gratuitous.

Completeness4/5

The purchase lifecycle is well covered end to end: browse/search, product detail, cart add/update/view, address, shipping, payment, review, place, and status. Gaps are minor but real: no post-purchase order tracking/history, and no explicit cart remove/clear (quantity 0 is a documented workaround).

Available Tools

18 tools
cart_addAInspect

Add units of a product to the customer's cart. The price is always the shop's own; it cannot be given. A product with variants needs its variant_id: without it you get need=options with the choices (the shop shows them as buttons): ask which one the customer wants and call again with that variant_id. If the product is already in the cart it returns already_in_cart and adds nothing (unless the customer asked for more in this message): to change how many there are, use cart_update with the exact number.

Inputs: product_id (required), qty, session_id, variant_id.

cart_updateAInspect

Change the quantity of a cart line (the key comes from cart_view). Quantity 0 removes the line.

Inputs: key (required), qty (required), session_id.

cart_viewB
Read-only
Inspect

The customer's cart: lines, quantities, prices and totals, as the shop calculates them.

Inputs: session_id.

check_availabilityA
Read-only
Inspect

Whether a product (or one of its variants) can be bought in a given quantity right now, and what that quantity costs: unit_price and total (unit price × quantity, calculated by the shop). When the customer asks how much several units cost, call it with that qty and say its total: never multiply yourself.

Inputs: product_id (required), qty, session_id, variant_id.

checkout_payment_optionsB
Read-only
Inspect

The payment methods offered for the order, with their kind (offline: transfer or cash on delivery; redirect: paid online) and any fee, and the one selected.

Inputs: session_id.

checkout_placeAInspect

Place the order. Needs the confirm_token of the last checkout_review, buyer_confirmed true (you declare that the person has seen the total and said yes) and one of two things: buyer_code, the 6-digit verification code that the shop emails to the buyer when you call checkout_review (ask the person for it and wait: never guess it), or an API key with the scope orders:create, sent as Authorization: Bearer. Without them nothing is placed. If anything changed after the review, the confirm_token is no longer valid: review again. The person pays: the answer says how.

Inputs: confirm_token (required), buyer_confirmed (required), buyer_code.

checkout_reviewA
Read-only
Inspect

The exact order that would be placed: lines, discounts, shipping, taxes, the total (total_cents and total formatted), the delivery address and the payment method, and the confirm_token that checkout_place needs. Read the total from here: never calculate it. If something is missing it says what. When no API key with the scope orders:create is sent, the shop emails a 6-digit verification code to the buyer for security and says so in "confirmation": tell the person, ask for the code and wait for it.

Inputs: session_id.

checkout_set_customerA
Read-only
Inspect

Save the customer's details for this order. Pass every detail in its OWN field, already separated: first_name, last_name, email, phone, line1 (street and number), line2 (floor and door), postcode, city, region, country, company and vat_id. Put only the value in each field, never the label or the sentence around it. Use text only as a last resort, when you cannot tell the details apart. It saves what is valid and returns what it understood, what is wrong and what is still missing. Never invent a value: ask for what was not said.

Inputs: city, note, text, email, +12 more.

checkout_set_paymentA
Read-only
Inspect

Choose the payment method (method = the id from checkout_payment_options).

Inputs: method (required), session_id.

checkout_set_shippingB
Read-only
Inspect

Choose the delivery option (carrier_id from checkout_shipping_options).

Inputs: carrier_id (required), session_id.

checkout_shipping_optionsA
Read-only
Inspect

The delivery options for the order with their price and delay, and the one selected. Needs the delivery address first.

Inputs: session_id.

checkout_statusA
Read-only
Inspect

Where the purchase is: what is still missing (contact, address, shipping, payment, in the order to ask for it), the cart summary and what is already saved. Personal data come masked. Call it before asking the customer anything about their order.

Inputs: session_id.

get_productA
Read-only
Inspect

Everything the shop says about one product: description in plain text, key facts, the options (colour, size) with their available values, variants with price and availability, delivery time and frequently asked questions. Call it whenever the customer asks about a product ("tell me about it", "what is it", "features") and answer with what it says.

Inputs: id (required), session_id.

list_categoriesC
Read-only
Inspect

The product categories of the shop with their sub-categories (what the shop sells), and popular: the categories of the best sellers, first the one that sells most.

Inputs: session_id.

search_productsA
Read-only
Inspect

Search the shop catalogue. Give words (query), a category, a maximum price in cents or only products in stock. Returns up to 8 products (id, name, price_formatted, available, summary, options such as colour or size) and answer_kind: exact (they match), relaxed or related (NOT exact: only the closest, say so), shop (a question about the shop, see shop_answer) or none (nothing matches: say so, never offer unrelated products).

Inputs: limit, query, session_id, category_id, +2 more.

shipping_quoteB
Read-only
Inspect

Delivery options, prices and times to a destination. Give the postcode (and the 2-letter country if it is not the shop's own). Quotes the product given, or the current cart when no product is given.

Inputs: qty, country, postcode, product_id, +2 more.

store_infoA
Read-only
Inspect

About the shop itself and its policies: what the shop is and sells in its own words (about), returns (the deadline and the text of the returns page, with its link), shipping and terms pages, accepted payment methods, how the invoice reaches the customer (invoices), contact details and opening hours. Call it for any question about the shop that is not about a product. Say you do not know only when this returns nothing for the topic.

Inputs: topic, session_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources