barrowman-associates-timeseries-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| config | No | Path to the JSON config file passed via --config CLI argument. | |
| OXBOW_CONFIG | No | Path to the JSON config file (alternative to --config). | |
| OXBOW_LOG_LEVEL | No | Log level (default INFO). | INFO |
| ANTHROPIC_API_KEY | No | Anthropic API key. Required only if provider.kind is 'real'. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_seriesA | Detect changepoints in a fleet metric and explain the most severe ones within the tenant's remaining monthly spend budget. points is a list of [unix_timestamp, value] pairs sorted by time. Returns the anomaly report including a per-changepoint audit trail. |
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 1 tool
With only a single tool, there is no possibility of confusion between tool purposes. The analyze_series tool has a clear, specific mandate to detect and explain changepoints.
The sole tool follows a clear verb_noun convention (analyze_series). No conflicting naming styles exist since there is only one tool.
A single tool feels too few for a server branded as a timeseries MCP. The broader domain typically requires multiple operations, making the tool count significantly under-scoped.
The server offers only changepoint analysis and lacks supporting operations such as data retrieval, transformation, or lifecycle management. This creates significant gaps for workflows that require more than the single analysis.