Tool Surface
This page summarizes the tool groups available on the Etalasse MCP server. Tools are task-shaped — not a one-to-one mirror of REST endpoints — which keeps inputs simple, authentication expectations clear, and tool names stable even when backend routes evolve.
For the complete, up-to-date list in your environment, call tools/list from your client, or open the MCP Console in the AI Workspace.
Naming convention
Tool names follow a group.action pattern, for example catalog.list_products or orders.update_status. Read groups generally provide list and get; write groups add create, update, and delete.
Tool groups
System and authentication
| Group | Example tools | Description |
|---|---|---|
| System | system.ping | Connectivity and server health check. |
| Dashboard auth | auth.dashboard_login, auth.dashboard_refresh | Manual Dashboard login and session refresh (fallback when OAuth is not used), including password change. |
Catalog (reads and writes)
| Group | Example tools | Description |
|---|---|---|
| Public shop and catalog | shop.get_by_username, catalog.list_products | Shop lookup and public product listing; accessible without a dashboard session. |
| Product management | catalog.create_product, catalog.update_product, catalog.list_variants, catalog.create_product_image | CRUD for products, variants, and product images. |
| Product reviews | reviews.list, reviews.summary, reviews.reported, reviews.hide, reviews.reply, reviews.bulk_moderate | Review inbox (filter by status, stars, photos, reported, no reply yet), summary, reported reviews, plus approve, reject, hide, show again, reply, pin, dismiss reports, and the approval setting. Replies and bulk actions are only sent after the merchant confirms. See Product Reviews. |
| Cross-sell | cross_sell.get_product, cross_sell.suggestions, cross_sell.set_links, cross_sell.settings, cross_sell.performance | Curated products and automatic suggestions per product, setting or reordering curated products (confirmed before a list is overwritten), settings, and cross-sell results. See Cross-sell. |
| Categories and add-ons | product_categories.create, addons.list, product_addons.overwrite_for_product | Product categories, add-ons with their details, and add-on-to-product mappings. |
| Digital assets | catalog.create_digital_asset, catalog.list_digital_assets | Managing digital assets sold as products. |
Orders and customers
| Group | Example tools | Description |
|---|---|---|
| Orders | orders.list, orders.get, orders.update_status | Reading orders and updating their status. |
| Customers | customers.list, customers.create | Shop customer records, including CRUD. |
Reports and analytics
| Group | Example tools | Description |
|---|---|---|
| Analytics | analytics.get_sales_overview | Sales performance overview. |
| Reports | reports.get_sales_performance, reports.get_product_performance, reports.get_inventory_report | Sales, product, customer, operations, payment, inventory, promotion, and delivery reports. |
| Storefront analytics | storefront_analytics.report, storefront_analytics.products, storefront_analytics.sources | Online store visits, shopping funnel, trend, top products, traffic sources (including UTM and Marketing Center links), devices, and in-store searches. Read-only; history follows the plan. |
Customer credit, webhooks and kitchen
| Group | Example tools | Description |
|---|---|---|
| Credit: read | credit.list_accounts, credit.get_account, credit.get_statement, credit.list_receivables, credit.get_receivable, credit.list_payments, credit.get_aging, credit.get_outstanding, credit.get_collections, credit.get_summary, credit.get_settings | Credit accounts, statements, invoices, payments, aging and summary. Read-only. See Customer Credit. |
| Credit: write | credit.create_account, credit.update_account, credit.preview_payment, credit.record_payment, credit.write_off, credit.remind_customer | Open and change accounts, record payments already received (requires confirmedAmount, safe to retry with the same requestId), write off debt with a reason, and send a reminder. Asks the merchant to confirm first. |
| Webhooks: read | webhooks.get_meta, webhooks.list, webhooks.get, webhooks.list_deliveries, webhooks.get_delivery, webhooks.list_events | Event catalogue, endpoints and the delivery log. The signing secret is never shown again. |
| Webhooks: write | webhooks.create, webhooks.update, webhooks.delete, webhooks.rotate_secret, webhooks.test, webhooks.redeliver, webhooks.replay_event | Manage endpoints with confirmation first. The secret appears only once, in the create and rotate responses. See Webhooks. |
| Kitchen: read | kitchen.list_stations, kitchen.get_routing, kitchen.get_queue, kitchen.get_ticket, kitchen.prep_time_report | Stations, routing, the ticket queue and the prep-time report. Read-only. See Kitchen Stations. |
| Kitchen: write | kitchen.create_station, kitchen.set_routing, kitchen.bulk_set_status, kitchen.void, kitchen.set_item_status, kitchen.recall, kitchen.set_rush | Station setup, routing, bulk bumps and voids ask for confirmation; bumping one item or ticket, recall and rush do not. Kitchen status never changes the order status. |
There are deliberately no MCP tools to enable, disable or bypass 2FA, or to read or reset sessions and recovery codes. These can only be done in the Dashboard (Settings > Security). An owner account with 2FA cannot sign in through auth.dashboard_login with email and password; use a personal access token or OAuth.
Bundles, referral, staff commission and labels
| Group | Example tools | Description |
|---|---|---|
| Bundles: read | bundles.list, bundles.get, bundles.preview, bundles.sale_lines | Bundles with counted stock, savings, margin and the limiting item; a preview writes nothing; what a bundle held on an order. Read-only. See Bundles. |
| Bundles: change | bundles.create, bundles.update | Create and edit bundles. Run a preview first and ask for confirmation (confirmed). Assembling, disassembling, refreshing prices and deleting are done in the Dashboard. |
| Referral: read | referral.get_settings, referral.list, referral.flagged_queue, referral.get, referral.report_summary, referral.top_referrers, referral.get_program, referral.resolve_code | Settings, referrals, the review queue, funnel report, top referrers, and the public program terms and code check (the code check counts as one funnel click). |
| Referral: change | referral.update_settings, referral.approve, referral.reject, referral.reverse | Change the promise and cost of rewards, approve, reject, or take back rewards. Asks the merchant for confirmation first. A customer's code, invites and claims are not MCP tools. |
| Staff commission: read | staff_commission.get_settings, staff_commission.summary, staff_commission.ledger, staff_commission.list_payouts | Rules, summary, the commission ledger, and payout history. Read-only. |
| Staff commission: change | staff_commission.update_settings, staff_commission.update_staff_rules, staff_commission.record_payout | Change rules (confirmation) and record a payout already made (needs a confirmedAmount equal to the server's figure; a changed figure answers AMOUNT_CHANGED). |
| Labels and last cost | labels.list_templates, labels.preview, labels.render_data, ingredients.last_purchase | Templates, print readiness, label data, and last purchase cost. Read-only; generating barcodes and printing are done in the Dashboard and POS. |
There are deliberately no MCP tools to set or reset staff PINs, create device enrolment codes, enrol or revoke POS devices, unlock a PIN, change PIN settings, or manage merchant or operator 2FA. They create or neutralise sign-in credentials, so they can only be done in the Dashboard.
Booking
| Group | Example tools | Description |
|---|---|---|
| Booking | booking.list_sessions, booking.create_session, booking.create_blocked_date | Booking sessions and blocked dates. |
| Booking: read | booking.list_bookings, booking.get_booking, booking.get_calendar, booking.get_availability, booking.list_staff, booking.get_staff, booking.get_settings, booking.get_report | Bookings by staff and date, booking detail and money, the calendar by staff, free slots, staff and their schedules, policy, and the no-show and deposit report. Read-only. |
| Booking: write | booking.reschedule, booking.mark_no_show, booking.collect_balance, booking.update_service, booking.set_staff_hours, booking.add_staff_time_off | Reschedule, mark no-show, record balance payment, service duration and deposit, staff schedule and time off. Asks for the merchant's confirmation first (confirmed). |
Promotions and retention
| Group | Example tools | Description |
|---|---|---|
| Flash sales | flash_sales.create, flash_sales.overwrite_details | Flash sales and their product details. |
| Coupons | coupons.list, coupons.create | Coupon codes and their rules. |
| Loyalty | memberships.create, membership_rewards.list, point_rewards.create, challenge_rewards.list | Memberships, membership rewards, point rewards, and challenge rewards. |
Finance
| Group | Example tools | Description |
|---|---|---|
| Withdrawals | withdrawals.create, withdrawals.get_current_balance, withdrawals.approve, withdrawals.pay | Withdrawals: requests, current balance, approval, payout, and rejection. |
| Payments and deliveries | payment_methods.create, bank_accounts.list, payments.toggle_active, deliveries.update_fee | Payment methods, bank accounts, and enabling/fee settings for payment and delivery channels. |
Content and storefront
| Group | Example tools | Description |
|---|---|---|
| Shop configuration | shop.get_config, shop.update | Reading and updating shop settings. |
| Content | banner.create, blogs.create, blog_categories.list, faqs.create | Banners, blogs, blog categories, and storefront FAQs. |
| Shop links and catalogs | shop_links.create, shop_catalogs.list | Shop links (Etalasse Link) and shop catalogs. |
| Shipping options | shipping_options.create | Shop shipping options. |
F&B
| Group | Example tools | Description |
|---|---|---|
| F&B | fnb_sales.create, fnb_tables.list_operational | F&B sales and table management, including operational table status. |
Inventory and stock
| Group | Example tools | Description |
|---|---|---|
| Stock | stocks.list, stock_in.create, stock_out.create, stock_return.create | Running stock plus stock-in, stock-out, lost, return, replacement, and stock sales movements. |
| Stock adjustments | stock_adjustments.list, stock_adjustments.create, stock_adjustments.bulk_create, stock_adjustments.report | Stock adjustment history, recording adjustments (single or bulk, with a reason), the reason list, and the stock loss report. Replaces the now-deprecated stock_lost.*, stock_return.*, and stock_replacement.*. |
| Stock count | stock_opnames.list, stock_opnames.get, stock_opnames.lines, stock_opnames.review | Read stock count sessions, their count lines, and the variance preview before finalizing. Read-only. |
| Inventory and suppliers | inventory.create, suppliers.list | Inventory master data and supplier records. |
Multivendor and staff
| Group | Example tools | Description |
|---|---|---|
| Resellers | resellers.create, resellers.list | Partners who resell your products. |
| Sellers | sellers.list, sellers.approve, sellers.balance, sellers.ledger, reports.sellers, seller_withdrawals.list | Vendors of a multivendor shop: seller approval and status, balances, ledger, report, and payouts. |
| Staffs | staffs.create, staffs.list | Shop staff accounts. |
Notifications
| Group | Example tools | Description |
|---|---|---|
| Notifications | notifications.list, notifications.mark_as_read, notifications.mark_all_as_read | Dashboard notifications, including read-state management. |
Customer and guest storefront flows
| Group | Example tools | Description |
|---|---|---|
| Customer auth | auth.customer_login, auth.customer_login_whatsapp, guest.create_session | Customer login (including via WhatsApp) and guest sessions. |
| Cart | cart.get_customer_cart, cart.add_guest_item, cart.update_customer_item | Reading and modifying customer and guest carts. |
| Checkout and orders | orders.create_customer_order, orders.create_guest_order, orders.cancel_customer_order | Creating, viewing, and cancelling customer/guest orders. |
Digital asset fulfillment
| Group | Example tools | Description |
|---|---|---|
| Digital fulfillment | orders.get_customer_digital_assets, orders.access_guest_digital_asset | Listing and accessing digital assets from customer and guest orders. |
Authentication rules per group
- Public tools (for example
shop.get_by_username,catalog.list_products) can be called without a dashboard session and accept an explicit shop identity. - Dashboard/admin tools require an authenticated session (OAuth or manual login) and always operate on the authenticated user's shop.
- Customer/guest tools use a customer session or a guest session created through the storefront auth tools.