Skip to main content
Glama

BRAINIAC Predictive & Customer Analytics

PELT changepoint detection

predictive-analytics_changepoint-detect
Read-onlyIdempotent

Detect mean or mean-variance changepoints with PELT, BIC/AIC or custom penalties, and MAD-based noise scaling. Price $0.03 USDC. POST /api/v1/predictive-analytics/changepoint-detect. 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>"
    },
    "name": "predictive-analytics_changepoint-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNomodel, string, one of mean, meanvar. Required.mean
valuesYesvalues, array. Required.
penaltyNopenalty, value. Required.bic
minSegmentNominSegment, integer, from 1 to 10000. Required.

Output Schema

NameRequiredDescriptionDefault
sigmaNosigma. Number.
sourcesNosources. Array.
segmentsNosegments. Array.
limitationsNolimitations. Array.
changepointsNochangepoints. Array.
penaltyValueNopenaltyValue. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds material context the annotations cannot: a fixed $0.03 USDC price, the x402 payment handshake, and the specific consequence that an unpaid call returns payment terms rather than a result. It stops short of describing output shape, but an output schema exists.

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?

Three short sentences, front-loaded with the capability, then cost/payment, then endpoint. Nothing is repeated from the title or annotations, and every clause carries information an agent needs.

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?

For a read-only, idempotent statistical tool with an output schema and full parameter coverage, the definition covers capability, cost, and payment failure behavior. The only minor omission is any hint about how MAD noise scaling or minSegment affect results, but the schema supplies the bounds.

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 coverage is 100% with terse field descriptions, so the baseline is 3. The description earns the extra point by mapping colloquial phrases to parameters: 'mean or mean-variance' explains the model enum, and 'BIC/AIC or custom penalties' clarifies that the penalty parameter accepts either a named criterion or a positive number, which the schema text ('penalty, value') does not.

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 states a specific verb and resource ('Detect mean or mean-variance changepoints with PELT') and enumerates the penalty options, so an agent knows exactly what statistical operation this performs. That is clearly separable from siblings such as correlation-analysis or kmeans-cluster without opening any schema.

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 no explicit guidance on when changepoint detection is the right choice versus the other analytics tools, nor any exclusions. The payment prerequisite ('an unpaid call returns the x402 payment terms and does not run') is the one practical usage rule given, which is useful but not a use-case routing rule.

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