get_capacity_alerts
ChatGPTReturn capacity alert summary and dated rows.
Business
Overview
Flowlity MCP Server lets authorized users inspect supply-chain sites, products, suppliers, orders, inventory, forecasts, promotions, capacity, alerts, imports, saved views, comments, and dashboard KPIs from Flowlity data through ChatGPT.
Tools
get_capacity_alerts
ChatGPTReturn capacity alert summary and dated rows.
get_comments
ChatGPTList planner comments on products and orders for a site. Comments are the free-text "qualitative why" a planner left next to a product or order — e.g. "FC revu suite info client" or "pic créé par la rétention des commandes en rupture". They are best read alongside the other MCP tools rather than alone: - pair with
get_forecast_accuracy to classify a bad MAPE as explained (promo, one-off order, data issue) vs unexplained; - pair with get_order_alerts / get_stock_coverage for stockout post-mortems; - cross-reference manual-override comments (rationale + author + date) with forecast value added; - reconcile commented promos against list_promotions. Filter with product_site_id and/or order_id to focus on one product or order, and date_from / date_to (inclusive, YYYY-MM-DD) to pull comments from a given period. Set unread_only=True for unread comments only. Results are ordered most-recent-first so recency weights relevance. Notes: - Text is inconsistent, multilingual (FR/EN/SV) and jargon-heavy (GC = grand compte, S11 = week 11, 1037363 --> 1041355 = substitution). Cite the source comment; never silently auto-action. - Coverage is uneven — absence of a comment is not absence of a problem. Comments are scoped to the site through their product, so legacy order-only comments without a product link are not returned.get_comments
ChatGPTList planner comments on products and orders for a site. Comments are the free-text "qualitative why" a planner left next to a product or order — e.g. "FC revu suite info client" or "pic créé par la rétention des commandes en rupture". They are best read alongside the other MCP tools rather than alone: - pair with
get_forecast_accuracy to classify a bad MAPE as explained (promo, one-off order, data issue) vs unexplained; - pair with get_order_alerts / get_stock_coverage for stockout post-mortems; - cross-reference manual-override comments (rationale + author + date) with forecast value added; - reconcile commented promos against list_promotions. Filter with product_site_id and/or order_id to focus on one product or order, and date_from / date_to (inclusive, YYYY-MM-DD) to pull comments from a given period. Set unread_only=True for unread comments only. Results are ordered most-recent-first so recency weights relevance. Notes: - Text is inconsistent, multilingual (FR/EN/SV) and jargon-heavy (GC = grand compte, S11 = week 11, 1037363 --> 1041355 = substitution). Cite the source comment; never silently auto-action. - Coverage is uneven — absence of a comment is not absence of a problem. Comments are scoped to the site through their product, so legacy order-only comments without a product link are not returned.get_demand_summary
ChatGPTReturn demand history and forecast summary for a product.
get_demand_summary
ChatGPTReturn demand history and forecast summary for a product.
get_forecast_accuracy
ChatGPTReturn MAPE/MAE/FVA forecast accuracy windows for one product.
get_forecast_accuracy
ChatGPTReturn MAPE/MAE/FVA forecast accuracy windows for one product.
get_forecast_history
ChatGPTReturn Flowlity forecast versions for one product, by target month. Shows how the monthly forecast for a given target month evolved across forecast runs (e.g. May-26 run forecasted Aug-26 = 30; Jun-26 run forecasted Aug-26 = 45). Rows are sorted by target month then by forecast run date (
updated_date) ascending, so the latest run is at the bottom of each target-month block. Forecasts are sourced from the Flowlity ML output at the site's configured granularity — ml.demand_forecast_flowlity_day_aggregated, _week_aggregated, or _month_aggregated depending on config.site_global.forecast_granularity (daily / weekly / monthly, default weekly). Day and week buckets are aggregated into calendar months via date_trunc('month', target_date); a bucket whose start date straddles a month boundary is attributed to the month containing its start. Forecast runs that happen within the same calendar month as the target are excluded so partial-month sums don't appear as a sudden revision (matches the dbt accuracy convention). Dates must be in YYYY-MM-DD format. target_month_start and target_month_end are inclusive and bound the target months covered.get_forecast_history
ChatGPTReturn Flowlity forecast versions for one product, by target month. Shows how the monthly forecast for a given target month evolved across forecast runs (e.g. May-26 run forecasted Aug-26 = 30; Jun-26 run forecasted Aug-26 = 45). Rows are sorted by target month then by forecast run date (
updated_date) ascending, so the latest run is at the bottom of each target-month block. Forecasts are sourced from the Flowlity ML output at the site's configured granularity — ml.demand_forecast_flowlity_day_aggregated, _week_aggregated, or _month_aggregated depending on config.site_global.forecast_granularity (daily / weekly / monthly, default weekly). Day and week buckets are aggregated into calendar months via date_trunc('month', target_date); a bucket whose start date straddles a month boundary is attributed to the month containing its start. Forecast runs that happen within the same calendar month as the target are excluded so partial-month sums don't appear as a sudden revision (matches the dbt accuracy convention). Dates must be in YYYY-MM-DD format. target_month_start and target_month_end are inclusive and bound the target months covered.get_import_status
ChatGPTReturn latest import status rows by site, dataset, or specific import id.
get_import_status
ChatGPTReturn latest import status rows by site, dataset, or specific import id.
get_kpi_trends
ChatGPTReturn monthly KPI trend points, with optional tag-level filtering. Valid
kpi values: demand_plan, inventory_level, supply_plan, stock_coverage, zero_stock_days. Units: demand_plan / inventory_level / supply_plan trends carry a quantity (default unit) and a value (EUR). stock_coverage is expressed in days of coverage (site average) — it has no value/currency dimension. zero_stock_days is a 0-1 rate shown as a percentage.get_kpi_trends
ChatGPTReturn monthly KPI trend points, with optional tag-level filtering. Valid
kpi values: demand_plan, inventory_level, supply_plan, stock_coverage, zero_stock_days. Units: demand_plan / inventory_level / supply_plan trends carry a quantity (default unit) and a value (EUR). stock_coverage is expressed in days of coverage (site average) — it has no value/currency dimension. zero_stock_days is a 0-1 rate shown as a percentage.get_monthly_demand_forecast
ChatGPTReturn demand and forecast bucketed by calendar month for a product. Use this tool for cross-year same-month comparisons (e.g. compare the forecast for Jul-26 against the actual demand for Jul-25 and Jul-24). Each row aggregates one calendar month between
start_date and end_date (inclusive, YYYY-MM-DD). Actual Demand is summed from public.demand (typically populated for past months); Final Forecast and Flowlity Forecast are summed from public.final_forecast (typically populated for current/future months). Use a date range that spans the years you want to compare.get_monthly_demand_forecast
ChatGPTReturn demand and forecast bucketed by calendar month for a product. Use this tool for cross-year same-month comparisons (e.g. compare the forecast for Jul-26 against the actual demand for Jul-25 and Jul-24). Each row aggregates one calendar month between
start_date and end_date (inclusive, YYYY-MM-DD). Actual Demand is summed from public.demand (typically populated for past months); Final Forecast and Flowlity Forecast are summed from public.final_forecast (typically populated for current/future months). Use a date range that spans the years you want to compare.get_order_alerts
ChatGPTGet order alert summaries and recent alert rows.
get_order_alerts
ChatGPTGet order alert summaries and recent alert rows.
get_product_constraints
ChatGPTReturn product-level planning constraints (coverage, min/max stock, shelf life). This is the product level (public.product_site): the inventory policy that constrains a product on its own, independent of supplier — minimum stock policy, target coverage days, maximum stock, shelf life and stock valuation price. Filter with `
product_ids and/or tag_ids. For supplier-specific MOQ/lead time/price/lot size use get_product_supplier_constraints`.get_product_constraints
ChatGPTReturn product-level planning constraints (coverage, min/max stock, shelf life). This is the product level (public.product_site): the inventory policy that constrains a product on its own, independent of supplier — minimum stock policy, target coverage days, maximum stock, shelf life and stock valuation price. Filter with `
product_ids and/or tag_ids. For supplier-specific MOQ/lead time/price/lot size use get_product_supplier_constraints`.get_product_detail
ChatGPTReturn full product details including tags, suppliers, alerts, and BOM.
get_product_detail
ChatGPTReturn full product details including tags, suppliers, alerts, and BOM.
get_product_planning
ChatGPTReturn planning time series for one product and date range.
get_product_planning
ChatGPTReturn planning time series for one product and date range.
get_product_supplier_constraints
ChatGPTReturn per-supplier sourcing constraints for products (MOQ, lead time, price, lot size). This is the product x supplier level (public.product_supplier_link): the MOQ, lead time, unit price, lot size and order frequency negotiated with each supplier for each product. Defaults to the primary supplier per product (highest active quota share, resolved from public.quota); set `
primary_supplier_only=False to list every supplier grouped by product x supplier. Filter with product_ids and/or tag_ids. For supplier-wide constraints (basket MOQ, full truck) use get_supplier_constraints; for product planning policy (coverage, min/max stock, shelf life) use get_product_constraints; for tag-based supply agreements use get_tag_constraints. When a row has a non-null Tag Family / Family MOQ, the line MOQ is enforced at the **tag-family scope** (sum over every product in the family >= Family MOQ) at sites where config.site_or.tag_family_moq is on. Audits like "MOQ vs forecast" should aggregate demand at the family level in that case, not per product. Use list_products(tag_ids=[<family_id>])` to enumerate the family.get_product_supplier_constraints
ChatGPTReturn per-supplier sourcing constraints for products (MOQ, lead time, price, lot size). This is the product x supplier level (public.product_supplier_link): the MOQ, lead time, unit price, lot size and order frequency negotiated with each supplier for each product. Defaults to the primary supplier per product (highest active quota share, resolved from public.quota); set `
primary_supplier_only=False to list every supplier grouped by product x supplier. Filter with product_ids and/or tag_ids. For supplier-wide constraints (basket MOQ, full truck) use get_supplier_constraints; for product planning policy (coverage, min/max stock, shelf life) use get_product_constraints; for tag-based supply agreements use get_tag_constraints. When a row has a non-null Tag Family / Family MOQ, the line MOQ is enforced at the **tag-family scope** (sum over every product in the family >= Family MOQ) at sites where config.site_or.tag_family_moq is on. Audits like "MOQ vs forecast" should aggregate demand at the family level in that case, not per product. Use list_products(tag_ids=[<family_id>])` to enumerate the family.get_promotion_detail
ChatGPTGet detailed promotion info and per-product impact rows.
get_promotion_detail
ChatGPTGet detailed promotion info and per-product impact rows.
get_site_config
ChatGPTFetch detailed site configuration and feature flags.
get_site_config
ChatGPTFetch detailed site configuration and feature flags.
get_site_kpis
ChatGPTReturn aggregated dashboard KPIs for a site.
get_site_kpis
ChatGPTReturn aggregated dashboard KPIs for a site.
get_stock_coverage
ChatGPTReturn stock-coverage metrics and optional low-coverage filter.
get_stock_coverage
ChatGPTReturn stock-coverage metrics and optional low-coverage filter.
get_stock_levels
ChatGPTReturn stock levels either by product or storage-site breakdown.
get_stock_levels
ChatGPTReturn stock levels either by product or storage-site breakdown.
get_supplier_constraints
ChatGPTReturn supplier-wide constraints (basket MOQ, full truck, order frequency). This is the supplier level (public.partner_site): constraints that apply to a whole order to a supplier rather than to one product line — the basket minimum order quantity, full-truck quantity, order frequency, max supplies per order and transportation lead time. Lists the suppliers used at the site. Filter with `
supplier_ids (partner_site IDs). For per-product MOQ/lead time/price/lot size use get_product_supplier_constraints`.get_supplier_constraints
ChatGPTReturn supplier-wide constraints (basket MOQ, full truck, order frequency). This is the supplier level (public.partner_site): constraints that apply to a whole order to a supplier rather than to one product line — the basket minimum order quantity, full-truck quantity, order frequency, max supplies per order and transportation lead time. Lists the suppliers used at the site. Filter with `
supplier_ids (partner_site IDs). For per-product MOQ/lead time/price/lot size use get_product_supplier_constraints`.get_tag_constraints
ChatGPTReturn tag-based supply-agreement constraints applied to products. This is the tag level (public.tag via public.product_tag_link): lot size and supply-agreement / supply-price rules defined once on a tag and shared by every product carrying it. Returns one row per product x constraint-tag. Filter with `
product_ids and/or tag_ids. Per-supplier MOQ/lead time/price lives in get_product_supplier_constraints; supplier-wide rules in get_supplier_constraints`.get_tag_constraints
ChatGPTReturn tag-based supply-agreement constraints applied to products. This is the tag level (public.tag via public.product_tag_link): lot size and supply-agreement / supply-price rules defined once on a tag and shared by every product carrying it. Returns one row per product x constraint-tag. Filter with `
product_ids and/or tag_ids. Per-supplier MOQ/lead time/price lives in get_product_supplier_constraints; supplier-wide rules in get_supplier_constraints`.list_capacity_units
ChatGPTList site capacity units with supplier and product counts.
list_capacity_units
ChatGPTList site capacity units with supplier and product counts.
list_orders
ChatGPTList order lines for a site with optional filters.
list_orders
ChatGPTList order lines for a site with optional filters.
list_product_alerts
ChatGPTList product alerts and summary counts by criticality.
list_product_alerts
ChatGPTList product alerts and summary counts by criticality.
list_products
ChatGPTSearch and list products with inventory and demand KPIs.
list_products
ChatGPTSearch and list products with inventory and demand KPIs.
list_promotions
ChatGPTList forecast events/promotions visible from the site context.
list_promotions
ChatGPTList forecast events/promotions visible from the site context.
list_sites
ChatGPTList accessible sites with key company and feature data.
list_sites
ChatGPTList accessible sites with key company and feature data.
list_tags
ChatGPTList tags available for a site's company and product links.
list_tags
ChatGPTList tags available for a site's company and product links.
list_views
ChatGPTList saved views for demand/planning modules on a site.
list_views
ChatGPTList saved views for demand/planning modules on a site.
