spss-studio-mcp

Overview Schema Source Related Servers Discussions Admin

Spss Correlations

spss_correlations

Compute Pearson or Spearman correlation matrices in IBM SPSS Statistics. Run CORRELATIONS analysis to examine relationships between variables.

Instructions

Run SPSS CORRELATIONS to compute Pearson or Spearman correlation matrix. Requires IBM SPSS Statistics to be installed.

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": {
      "file_path": "<file_path>",
      "variables": "<variables>"
    },
    "name": "spss_correlations"
  }
}

Input Schema

Name	Required	Default
`method`	No	pearson
`file_path`	Yes
`variables`	Yes
`two_tailed`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the external SPSS dependency, which is genuinely useful, but says nothing about runtime behavior, side effects, error handling, or whether the underlying data is modified. For a computation tool with zero annotation coverage this is thin.

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?

Two short sentences, front-loaded with the action and the method choice, with no filler. Every clause earns its place.

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

Completeness2/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 described, but with no usage guidance and 0% parameter documentation the agent lacks enough to invoke this correctly beyond guessing at file_path/variables semantics.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters. The description mentions Pearson/Spearman, but that merely restates the enum already present in the schema; file_path, variables, and two_tailed receive no explanation, so the description fails to compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: run SPSS CORRELATIONS and compute a Pearson or Spearman correlation matrix. This clearly distinguishes it from regression, crosstabs, and other statistical siblings in the list, though it does not name an alternative explicitly.

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 only guidance is the prerequisite that IBM SPSS Statistics must be installed. There is no indication of when to choose correlations over, say, regression or crosstabs, nor any exclusion conditions.

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

Deploy Server