forecast-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| forecastC | Forecast a single numeric time series. |
| list_backendsA | Report which forecasting engine is active and why. |
| backtestB | Hold out the last N points and compare TimesFM vs baseline performance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct, non-overlapping purpose: backtesting, forecasting, and engine info. No ambiguity between them.
All tools use imperative verbs, but 'backtest' and 'forecast' are single words while 'list_backends' uses an underscore. Slight inconsistency in formatting.
Three tools is well-scoped for a focused forecasting server. Each tool is essential and contributes to the core workflow.
Covers the main actions: forecast, backtest, and engine info. Minor gaps like listing available models or settings, but acceptable for this domain.