Skip to main content
Glama

BRAINIAC Predictive & Customer Analytics

Pearson, Spearman, Kendall and partial correlations

predictive-analytics_correlation-analysis
Read-onlyIdempotent

Pairwise Pearson/Spearman/Kendall correlations with p-values, optional partial correlations, and Holm/BH/Bonferroni adjustment across pair-method tests. Price $0.03 USDC. POST /api/v1/predictive-analytics/correlation-analysis. 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": {
      "columns": "<columns>",
      "rows": "<rows>"
    },
    "name": "predictive-analytics_correlation-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYesrows, array. Required.
adjustNoadjust, string, one of none, holm, bh, bonferroni. Required.none
columnsYescolumns, array. Required.
methodsNomethods, array. Required.
partialNopartial, array. Optional.

Output Schema

NameRequiredDescriptionDefault
capsNocaps. Object.
pairsNopairs. Array.
partialNopartial. Array.
sourcesNosources. Array.
rowsUsedNorowsUsed. Number.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false), so the lower bar applies. The description adds genuinely useful operational context: the $0.03 USDC price, the POST endpoint, and crucially that an unpaid call returns x402 payment terms without running the analysis. It does not mention data-size limits or error behavior, so it stops short of a 5.

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 tight sentences: the capability comes first, and the payment and endpoint details come last. There is no padding, and the payment-gate caveat is stated plainly.

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 not be explained, and the description covers capability, cost, transport, and the payment failure mode. Remaining gaps, such as input data shape expectations (rows aligned to columns) and limits on row or column counts, are modest for a read-only analytics endpoint.

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 100%, so the schema documents all five parameters, including enums and defaults. The description adds conceptual meaning for `partial` (optional partial correlations) and clarifies that adjustment applies 'across pair-method tests', but it does not explain the nested `given` conditioning set or the rows/columns alignment constraint.

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 names a specific computation (pairwise Pearson/Spearman/Kendall correlations with p-values), plus optional partial correlations and multiple-testing adjustment. That is enough for an agent to distinguish it from siblings such as predictive-analytics_pca or predictive-analytics_cox-regression without opening the schema.

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 says what is computed but never states when to choose this tool over alternatives, nor any prerequisites, such as requiring numeric columns or enough rows for stable p-values. Guidance is limited to what can be inferred from the name and method list.

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