timeseries-mcp

rolling_stats

Calculate rolling-window statistics on a time series, including mean, standard deviation, min, max, and median, over a specified window size.

Instructions

Rolling-window statistics with an evenly spaced preview per stat.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "series_id": "<series_id>",
      "window": "<window>"
    },
    "name": "rolling_stats"
  }
}

Input Schema

Name	Required	Description
`stats`	No	Which rolling statistics to compute.
`window`	Yes	Window size in observations.
`series_id`	Yes

Output Schema

Name	Required	Description	Default
`stats`	Yes
`window`	Yes
`series_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Without annotations, the description must carry behavioral transparency. It mentions 'evenly spaced preview' but doesn't explain what that entails (number of points, how spacing works). No disclosure of performance implications or idempotency. Adds some value but insufficient.

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 sentence, front-loaded with the core action. No redundant words or filler. Efficient and direct.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be detailed. However, the description lacks context on usage within the suite of sibling tools (many time-series operations). The 'evenly spaced preview' concept is undefined, and required parameter 'series_id' is unexplained.

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

Parameters3/5

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

Schema coverage is 67% (series_id lacks description). The description adds no parameter-level details beyond what the schema already provides. For the undocumented series_id, the description fails to compensate.

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 it computes rolling-window statistics with a preview, distinguishing it from siblings like 'get_window' (single window) or 'describe' (summary stats). The verb 'rolling-window statistics' and resource 'per stat' are specific.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives (e.g., 'get_window', 'describe', 'data_quality'). No explicit when/when-not or mention of prerequisites.

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

Deploy Server