Skip to main content
Glama

predict_forecast

Read-onlyIdempotent

Forecast future values from historical time series data using ARIMA or Holt-Winters models. Provides point forecasts with confidence bands for demand planning, KPI projection, and capacity forecasting.

Instructions

[Premium] Project future values from a univariate time series using ARIMA or Holt-Winters (additive seasonal). Use for short-to-medium horizon point forecasts with confidence bands: demand planning, KPI projection, capacity forecasting. ARIMA suits non-seasonal trend data; Holt-Winters handles repeating seasonality (set seasonLength). Needs at least ~20 observations for stable fit. For point-anomaly flags rather than projection, use detect_anomaly. Requires ORACLAW_API_KEY.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesHistorical values, evenly spaced. ARIMA needs ≥20 points; Holt-Winters needs ≥2 × seasonLength.
stepsYesNumber of future periods to forecast.
methodNoDefault: arima.
seasonLengthNoPeriod of seasonality (only used by holt-winters). Default: 4.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
forecastYesPoint forecasts, length = steps.
confidenceNo
modelNoFitted model description.
methodYes
inputLengthNo
stepsYes
Behavior4/5

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

Annotations declare read-only and idempotent, but description adds premium tier, API key requirement, and confidence bands. No contradiction.

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?

Single efficient paragraph, front-loaded purpose, no fluff, every sentence adds value (use case, model choice, requirements, alternative).

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?

Covers all key aspects: purpose, model selection, data needs, API key, premium tier, and alternative tool, despite presence of output schema (not shown).

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 has 100% description coverage, so baseline 3. Description adds method selection guidance and data constraints (e.g., Holt-Winters needs 2× seasonLength), beyond 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?

Description clearly states projecting future values from univariate time series using ARIMA or Holt-Winters, specifies use cases (demand planning, KPI projection), and distinguishes sibling detect_anomaly.

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?

Explicitly tells when to use ARIMA vs Holt-Winters based on data seasonality, mentions observation requirements, and directs to detect_anomaly for anomaly detection instead.

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/Whatsonyourmind/oraclaw'

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