Skip to main content
Glama

BRAINIAC Statistics & Quality Engineering

Decompose a seasonal time series

statistics_time-series-decompose
Read-onlyIdempotent

Classical moving-average additive or multiplicative decomposition into trend, seasonal indices and remainder, with Wang-Smith-Hyndman strength of seasonality and trend measures. STL is not provided. Price $0.03 USDC. POST /api/v1/statistics/time-series-decompose. An unpaid call returns the x402 payment terms and does not run.

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": {
      "values": "<values>",
      "period": "<period>"
    },
    "name": "statistics_time-series-decompose"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNomodel, string, one of additive, multiplicative. Required.additive
periodYesperiod, integer, from 2 to 366. Required.
valuesYesvalues, array. Required.

Output Schema

NameRequiredDescriptionDefault
modelNomodel. String.
trendNotrend. Array.
periodNoperiod. Number.
sourcesNosources. Array.
seasonalNoseasonal. Array.
remainderNoremainder. Array.
limitationsNolimitations. Array.
trendStrengthNotrendStrength. Number.
seasonalIndicesNoseasonalIndices. Array.
seasonalStrengthNoseasonalStrength. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open world), and the description adds genuinely non-obvious behavior: a $0.03 USDC charge, the POST endpoint, and the fact that an unpaid x402 call returns payment terms without executing. It does not address data prerequisites for classical decomposition (e.g. needing at least two full periods), which is the remaining behavioral gap.

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?

Front-loaded with the method and outputs, then the STL exclusion, then billing and transport details. Dense but every clause carries information; the raw endpoint path is the only near-redundant element.

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?

An output schema exists so return values need no explanation, and the payment gate is disclosed. What is missing is input adequacy guidance — minimum series length relative to period, and handling of short or zero-valued series for the multiplicative model — which matters for a decomposition call to succeed.

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 description coverage is 100%, so the additive/multiplicative enum and the 2-366 period bound are already documented. The description only echoes the model choice in prose and adds no meaning about how period interacts with series length.

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?

Names the specific method (classical moving-average decomposition) and the exact outputs (trend, seasonal indices, remainder) plus the Wang-Smith-Hyndman strength measures. It also pre-empts the most likely confusion by stating 'STL is not provided', which no sibling tool name would resolve.

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

Usage Guidelines3/5

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

There is an implicit exclusion (no STL) but no positive guidance on when to pick additive vs multiplicative, or when decomposition is the right choice over the regression/nonparametric siblings. The agent must infer the use case from the method name alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources