forecast-mcp

forecast_series

Forecasts future demand for any SKU by automatically classifying its sales pattern and routing to the optimal model—mean fallback, TSB, or AutoETS—for accurate results.

Instructions

Forecast future demand for a SKU. Automatically classifies the series first and routes to the matching model: mean fallback for cold-start SKUs, TSB for intermittent demand, AutoETS for regular continuous demand.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "unique_id": "<unique_id>"
    },
    "name": "forecast_series"
  }
}

Input Schema

Name	Required	Description	Default
`horizon`	No	number of days ahead to forecast (default 14).
`unique_id`	Yes	SKU identifier. Call list_skus() to see what's available.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 18, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden. It reveals the internal routing logic (mean fallback, TSB, AutoETS) but does not mention authorization needs, error behavior, or operational constraints such as required permissions or data prerequisites.

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

Conciseness5/5

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

The description is concise with two sentences. The first sentence states the core purpose, and the second elaborates on the internal routing. Every word serves a purpose, no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity, an output schema exists, and parameters are well-covered in the schema, the description covers the essential algorithmic behavior. It could mention prerequisites (e.g., valid SKU) or edge cases, but overall it is reasonably complete.

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%, so baseline is 3. The description adds no additional meaning to parameters beyond what the schema already provides (horizon default/description, unique_id description with pointer to list_skus). The description does not elaborate on parameter usage or constraints.

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 verb 'Forecast future demand' and the resource 'a SKU'. It distinguishes from siblings by explaining the automatic classification and routing to different models, making the unique purpose evident.

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

Usage Guidelines3/5

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

The description implicitly indicates when to use this tool (to forecast a SKU's demand) but does not explicitly state when not to use it or suggest alternatives like classify_demand_pattern or evaluate_forecast for related tasks. The context is clear but lacks exclusion guidance.

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

Deploy Server