Skip to main content
Glama
S-FM
by S-FM

forecast

Predict future values from time series data using point or probabilistic outputs. Supports univariate and multivariate series with Chronos2 or TiRex models.

Instructions

Perform time series forecasting using FAIM platform. Supports both point forecasting (single value) and probabilistic forecasting (confidence intervals). Can handle univariate and multivariate time series data. Currently supported models: Chronos2 (default, recommended for multivariate) and TiRex (fast, univariate only).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modelYesThe forecasting model to use. Chronos2: State-of-the-art, supports univariate/multivariate, custom quantiles. TiRex: Fast alternative for univariate only, uses fixed quantiles [0.1,0.2,...,0.9], custom quantiles parameter ignored.
xNoTime series data to forecast from. MUST be an array, NOT a string. Can be a 1D array [1,2,3,4,5], 2D array [[1,2],[3,4]] (multiple series/batch or multivariate per model), or 3D array [[[1],[2]]] (batch, sequence, features). Never pass x as a JSON string - always pass as an actual array.
horizonYesNumber of time steps to forecast into the future. Must be a positive integer. Example: 10 means predict the next 10 steps.
output_typeNoType of forecast output. "point" = single value per step (fastest). "quantiles" = confidence intervals (use for uncertainty estimation). Default: "point".
quantilesNoCustom quantile levels to compute (only used with output_type="quantiles" and Chronos2 model). For TiRex, this parameter is ignored and fixed quantiles [0.1,0.2,0.3,0.4,0.5,0.6,0.7,0.8,0.9] are always returned. Values must be between 0 and 1. Example: [0.1, 0.5, 0.9] for 10th, 50th, 90th percentiles.
is_multivariateNoFor 2D input arrays only with Chronos2: interpret as multivariate time series (true) or batch of univariate series (false, default). Ignored for 1D arrays, 3D arrays, and TiRex model.
Behavior4/5

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

With no annotations, the description carries full burden. It discloses output types (point vs quantiles), model-specific behavior (TiRex ignores custom quantiles, returns fixed quantiles), and input shape constraints (MUST be array, not string). It does not cover rate limits or cost, but is transparent about core behavior.

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 (3 sentences) with no fluff. First sentence states core purpose, second covers capabilities, third lists models. Every sentence provides essential information.

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 6 parameters, no output schema, and a sibling tool, the description covers tool purpose, model selection criteria, input format constraints, and output types. It lacks description of return value structure, but without output schema this is acceptable. For a complex forecasting tool, it is fairly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 significant value beyond schema: explains model differences, input shape nuances, default output type, and the meaning of is_multivariate for Chronos2 with 2D arrays. This extra context justifies a 4.

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 that the tool performs time series forecasting, distinguishes between point and probabilistic forecasting, and explicitly lists supported models (Chronos2, TiRex). It differentiates from the sibling tool list_models by focusing on forecasting actions rather than model listing.

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

Usage Guidelines4/5

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

The description provides guidance on when to use each model (e.g., 'Chronos2...recommended for multivariate', 'TiRex...fast, univariate only') and input shape requirements. It could be improved by explicitly stating when not to use the tool, but the sibling tool list_models covers model selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/S-FM/faim-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server