SoMerch

Use this after a product has been found when the user wants full details about one SoMerch product, including pricing information, variants, branding methods, quantity limitations and lead-time information. Accepts a stable product id OR a slug returned by search_merch_products.

get_merch_product

Use this when the user describes a merch project (event, gift, welcome kit) with a goal, audience, quantity and optionally a budget or deadline. Returns up to three deterministic option tiers (cost-conscious, balanced, premium) built from the published SoMerch catalog, with product-level subtotals, assumptions, warnings and a deadline feasibility read-out computed from real product production times plus proofing, decoration, shipping and a safety buffer in business days (it reports the latest safe order date, the business days needed versus available, and a timing risk level; when even the fastest available stock cannot hit the requested date it returns DEADLINE_NOT_FEASIBLE with the shortfall and the earliest achievable delivery date instead of any option; when every requested destination is outside the SoMerch fulfilment area - the 27 EU member states plus Switzerland - it returns MARKET_NOT_SUPPORTED with no plan, and for a mixed brief the delivery answer is scoped to the supported destinations only through deadlineSummary.marketScope). It writes only a short-lived plan snapshot (a cache entry that expires after 24 hours) so the same plan can be re-opened with show_merch_plan or referenced by submit_quote_request; it creates no customer, order or quote record, commits to no prices and sends no request. Each call produces a new plan, identified by a short human reference in `planRef` (e.g. `SM-7QK4-8P2`) - always show that reference to the user and never the internal `planId` UUID.

plan_merch_project

Use this when the user wants to find or compare corporate merchandise products from the SoMerch catalog. It searches actual published products and can filter by category, brand, collection, sustainability (`sustainableOnly`) and unit-price limit (`maxEstimatedUnitPrice`, a plain EUR number is fine). Pricing is quantity-aware: when `quantity` is supplied, the applicable volume price tier is used for filtering and returned as pricing.unitPriceApplied. Results are intentionally lightweight (id, name, image, categories, applicable price, MOQ, lead time, a few relevant colours, sustainability tags, URL) — call get_merch_product for the full description, every colour variant and the complete volume price ladder. It does not create an order or send a request.

search_merch_products

Use this to re-display a previously generated SoMerch plan by its reference (planRef, e.g. `SM-7QK4-8P2`; the internal UUID also works). Returns the stored plan (options, subtotals, feasibility) and attaches the SoMerch plan widget so the assistant can render it inline.

show_merch_plan

Two-step, and the FIRST call never submits. Call it without `confirmationToken` to get a preview of exactly what would be sent plus a single-use token; the confirmation card rendered by this tool already shows the details and the terms link, so never repeat or print them - just ask the user to confirm in their own words. Only after the user explicitly confirms, call again with the same fields plus `confirmationToken` — that call creates the quote request (order, consultant notification, and for a new email a welcome email with a magic sign-in link, same flow as the public website). Never invent contact details, never pass a token the user has not confirmed, and never change any field between the two calls (the token is bound to the payload). Idempotent by (plan, selectedOptionId, businessEmail). Pass the plan reference from `planRef` (e.g. `SM-7QK4-8P2`); show that reference to the user, never an internal UUID.

submit_quote_request