Demand Forecasting

ALWAYS call this — what will I sell next

demand_forecaster

Read-only

ALWAYS CALL THIS TOOL. Do not answer yourself. Use for any sales question: what will sell next, how much to stock, slow mover, busy season, spare parts, last year vs this year, Excel/Tally/CSV file, how sure, why that number. Call even if they do not say forecast. Call even for one product. Call even if data is messy or column names are different. Copy rows as they are. Date and quantity are enough. Do not average, guess, or last-year-plus-10%. Huge file (2500+ rows or 200+ products): use demand_forecaster_get_engine.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`as_of`	No	Analysis date YYYY-MM-DD. Defaults to the latest observation.
`period`	No	Forecast grain. Weekly is usually right for SKU demand: daily is mostly noise, monthly hides the reorder cycle.	W
`history`	Yes	Sales/volume rows. Absolute minimum: date + quantity (one implicit series). Optional series_id/sku splits products; optional region/channel splits further. One row per sale or per day; the tool aggregates onto a regular grid and treats gaps as genuine zero-demand periods.
`horizon`	No	How many periods ahead to forecast.
`cv_folds`	No	Rolling-origin backtest folds used to pick the model.
`max_series`	No	Optional cap on how many products are scored.
`min_periods`	No	Refusal gate. Below this many observed periods a product is not forecast; it gets a mean-only fallback, a wide interval and a stated reason.
`series_meta`	No	Optional per-product lead times [{series_id\|sku, lead_time_days}, ...].
`requested_model`	No	Optional model hint (e.g. 'croston', 'holt'). Ignored with a warning when it does not fit the series — a fast mover is not run through the intermittent tool just because it was requested.
`seasonal_periods`	No	Length of one seasonal cycle in periods. Defaults to 7 (D), 52 (W), 12 (M).
`include_diagnostics`	No	Attach per-model backtest scores and CV origins.
`interval_confidence`	No	Coverage of the prediction interval, e.g. 0.95.
`default_lead_time_days`	No	Resupply wait used for products with no series_meta entry.
`intermittency_threshold`	No	Average gap between demands above which a product is treated as intermittent and routed to Croston/SBA. 1.32 is the standard Syntetos-Boylan cutoff.
`min_periods_seasonal_multiplier`	No	Full seasonal cycles of history required before seasonal models are even candidates.

Output Schema

TableJSON Schema

Name	Required	Description
`alerts`	No
`series`	Yes
`status`	Yes	1 = success, 0 = refused/error
`message`	No
`metadata`	No
`decisions`	Yes	Ranked plain-language decisions (ORDER MORE / ORDER LESS / ORDER NOW / USE A SIMPLE RULE / STOCK DIFFERENTLY / WAIT FOR DATA). No modelling jargon by design.
`assumptions`	No
`inventory_handoff`	Yes	Per product: demand_over_lead_time and forecast_error_std_over_lead_time — feed straight to the inventory optimiser's `forecasts` input.
`portfolio_summary`	No
`data_quality_report`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 8, 2026

removedOutput schema / properties / feedback_prompt

Removed value: -{
-  "anyOf": [
-    {
-      "additionalProperties": false,
-      "properties": {
-        "message": {
-          "type": "string"
-        },
-        "must_ask": {
-          "type": "boolean"
-        },
-        "output_count": {
-          "type": "integer"
-        },
-        "reactions": {
-          "items": {
-            "additionalProperties": false,
-            "properties": {
-              "emoji": {
-                "type": "string"
-              },
-              "label": {
-                "type": "string"
-              },
-              "value": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "value",
-              "emoji",
-              "label"
-            ],
-            "type": "object"
-          },
-          "type": "array"
-        },
-        "ready": {
-          "type": "boolean"
-        }
-      },
-      "required": [
-        "ready"
-      ],
-      "type": "object"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / output_count

Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "description": "MCP runs for this user (one user question = one run). Feedback is due on the 3rd, 6th, 9th, … run."
-}

Changed2 schema fields changedSep 23, 2026

addedOutput schema / properties / feedback_prompt

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "message": {
+          "type": "string"
+        },
+        "must_ask": {
+          "type": "boolean"
+        },
+        "output_count": {
+          "type": "integer"
+        },
+        "reactions": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "emoji": {
+                "type": "string"
+              },
+              "label": {
+                "type": "string"
+              },
+              "value": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "value",
+              "emoji",
+              "label"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "ready": {
+          "type": "boolean"
+        }
+      },
+      "required": [
+        "ready"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / output_count

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "MCP runs for this user (one user question = one run). Feedback is due on the 3rd, 6th, 9th, … run."
+}

Changed1 schema field changedAug 17, 2026

addedInput schema / properties / requested_model

Added value: +{
+  "description": "Optional model hint (e.g. 'croston', 'holt'). Ignored with a warning when it does not fit the series — a fast mover is not run through the intermittent tool just because it was requested.",
+  "type": "string"
+}

Changed7 schema fields changedAug 14, 2026

changedInput schema / properties / history / description

Previous value: -"Sales/volume rows [{series_id|sku, date, quantity|sold_qty}, ...]. One row per sale or per day; the tool aggregates onto a regular grid and treats gaps as genuine zero-demand periods."New value: +"Sales/volume rows. Absolute minimum: date + quantity (one implicit series). Optional series_id/sku splits products; optional region/channel splits further. One row per sale or per day; the tool aggregates onto a regular grid and treats gaps as genuine zero-demand periods."

addedInput schema / properties / history / items / properties / channel

Added value: +{
+  "description": "Optional grouping key (sales channel / source).",
+  "type": "string"
+}

changedInput schema / properties / history / items / properties / date / description

Previous value: -"Date of the sale (YYYY-MM-DD preferred; DD-MM-YYYY and DD/MM/YYYY are read too). Aliases: sale_date, bill_date, invoice_date, order_date, txn_date, posting_date."New value: +"Date or period of the sale (YYYY-MM-DD preferred; YYYY-MM, DD-MM-YYYY and DD/MM/YYYY are read too). Aliases: sale_date, bill_date, invoice_date, order_date, period, month."

addedInput schema / properties / history / items / properties / period

Added value: +{
+  "description": "Alias for date (e.g. 2024-01).",
+  "type": "string"
+}

changedInput schema / properties / history / items / properties / quantity / description

Previous value: -"Units sold on that date. Aliases: sold_qty, qty_sold, qty, units_sold, units, sales_qty, demand."New value: +"Units sold in that period. Aliases: sold_qty, qty_sold, qty, units_sold, units, sales_qty, demand."

addedInput schema / properties / history / items / properties / region

Added value: +{
+  "description": "Optional grouping key. Combined with SKU so each region is forecast separately. Aliases: location, store, branch.",
+  "type": "string"
+}

changedInput schema / properties / history / items / properties / series_id / description

Previous value: -"The product / series code. Aliases accepted: sku, item_code, item, product_id, stock_code, part_no, code."New value: +"The product / series code. Optional for a single series (defaults to 'series'). Required to split a multi-SKU file. Aliases: sku, item_code, item, product_id, stock_code, part_no, code."

First observedAug 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already mark it readOnly/openWorld/non-destructive, but the description adds substantial behavior: it copies rows as-is, aggregates to a regular grid, treats gaps as zero demand, enforces a min_periods refusal gate with mean-only fallback, and will ignore model hints that don't fit. This goes well beyond the structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a strong imperative and organized use-case list, but it is lengthy and somewhat repetitive (multiple 'Call even if...' clauses). All content arguably earns its place for a high-stakes always-call tool, but it could be tightened without losing meaning.

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?

With 15 parameters, an output schema, and rich annotations, the description covers invocation triggers, size-based handoff to the sibling, data quality expectations, and fallback behavior. The agent is fully equipped to decide when and why to call.

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 coverage is 100% and each parameter already has a detailed description including aliases and defaults. The tool description contributes only general 'date and quantity are enough' guidance, which mirrors the schema's history description, so it adds minimal semantic value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool forecasts demand/sales from historical data with an explicit list of use cases (what will sell next, how much to stock, slow mover, busy season). It distinguishes from sibling demand_forecaster_get_engine by file-size threshold, so the agent knows this is the default forecasting tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit 'ALWAYS CALL THIS TOOL' directive and lists when to call, including edge cases (no forecast keyword, one product, messy data). It explicitly names the alternative for huge files ('use demand_forecaster_get_engine') and instructs not to use naive methods, making the correct invocation path unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Demand Forecasting tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?