MCP forecasting tool design

MCP forecasting tool design

Build a forecasting tool around your chosen execution provider and an inspectable numerical contract.

Supply the compute separately

MCP defines a tool interface, not a forecasting execution service. A forecasting server must call your external provider or local implementation. TSFM does not offer a public forecasting MCP endpoint; its browser demo is not a remote MCP server.

Validate before execution

Require a resolved target series, units, cadence, cutoff, and horizon. Check task and input support against the actual checkpoint. Keep credentials in the tool implementation and return errors explicitly when a provider is unavailable or rejects the input.

Return evidence an assistant can inspect

Include model revision, issue time, quantile levels, and forecast values alongside source provenance and limitations. An assistant should distinguish forecasts from observed outcomes and identify failed or unsupported computations rather than inventing values.

Resources