Skip to main content
Glama

forecast

Predict future values from time series data using Geneva's automated forecasting engine, which selects optimal models for accurate projections.

Instructions

Run the Geneva Forecasting Engine on a time series and return forecast results.

Use this tool when the user has numerical time series data (e.g., monthly sales, daily temperatures, quarterly revenue) and wants to predict future values. The Geneva Expert System automatically selects the best forecasting model from 10 methods including exponential smoothing, Holt-Winters, and regression models.

Parameters

data : list[float] Time series observations. Minimum 3 data points, maximum 10,000. These should be sequential, evenly-spaced numerical values. horizon : int, optional Number of future periods to forecast. Default: one full seasonal cycle (e.g., 12 for monthly data). For monthly data, 18 is a good choice. For quarterly, 8. For weekly, 13. wave_periods : list[int], optional Seasonal cycle lengths. IMPORTANT — set this correctly for your data: - [12] for monthly data (default) - [4] for quarterly data - [52] for weekly data - [7] for daily data - [24] for hourly data - [1] for yearly/non-seasonal data confidence_level : float Prediction interval confidence (0.0 to 1.0). Default 0.95 gives 95% prediction intervals. Higher = wider bands, more confidence. method : int, optional Force a specific forecasting method (0–9). Omit to let the Expert System auto-select the best model. Methods: 0=LinearReg, 1-5=NonLinearReg, 6=SES, 7=DES (Double Exponential Smoothing), 8=HoltWinters, 9=Croston. Expert System (default) tries all and picks the best fit. seasonal_transform : int Seasonal transform to apply: 0=None (default), 1=Seasonal, 2=MPT (Moving Periodic Total). Use 1 or 2 for strongly seasonal data to improve forecast accuracy. smoothing : bool Enable median data smoothing (3-period window). Useful for noisy data. Default: False. max_periods_factor : float, optional Controls the fit window cap (nPPC × MPF). Higher values give the model more holdout data for evaluation, which can improve accuracy on long series. Default: engine default (1.5). Use 10+ for long series. Max: 100. holdout_ratio : float, optional Fraction of data reserved for model evaluation (e.g., 0.333). Default: engine default (1/3).

Returns

CallToolResult Contains a text summary with forecast values, accuracy metrics, model info, and prediction intervals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes
horizonNo
wave_periodsNo
confidence_levelNo
methodNo
seasonal_transformNo
smoothingNo
max_periods_factorNo
holdout_ratioNo
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: the tool automatically selects the best forecasting model from 10 methods, handles optional parameters with defaults, and returns a text summary with forecast values and metrics. It could improve by mentioning computational requirements or error handling, but it covers the core operation well.

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 well-structured with clear sections (purpose, usage, parameters, returns) and uses bullet points for wave_periods examples. While comprehensive, it is appropriately sized for a complex tool with many parameters. Some sentences could be tightened (e.g., the horizon explanation is slightly verbose), but overall it's efficient and front-loaded.

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 complexity (9 parameters, no annotations, no output schema), the description is largely complete. It covers purpose, usage, detailed parameter semantics, and return format. However, it lacks explicit information about error conditions, rate limits, or authentication needs, which would be helpful for full contextual understanding.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description fully compensates by providing detailed semantic information for all 9 parameters. It explains each parameter's purpose, default values, valid ranges (e.g., data length 3-10,000, confidence_level 0.0-1.0), and practical guidance (e.g., wave_periods settings for different data frequencies, method codes). This adds significant value beyond the bare 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's purpose: 'Run the Geneva Forecasting Engine on a time series and return forecast results.' It specifies the verb ('Run'), resource ('Geneva Forecasting Engine'), and outcome ('return forecast results'), with examples of applicable data types (e.g., monthly sales, daily temperatures). With no sibling tools, this level of specificity is excellent.

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 explicitly states when to use the tool: 'Use this tool when the user has numerical time series data... and wants to predict future values.' It provides clear context for application, including data requirements and the user's intent. With no sibling tools, no alternative guidance is needed.

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/RoadMap-Tech/geneva-mcp'

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