spss-studio-mcp

Overview Schema Source Related Servers Discussions Admin

Spss Regression

spss_regression

Run SPSS linear regression by specifying a dependent variable and predictors to get coefficients, R-squared, ANOVA, and significance tests. Requires IBM SPSS Statistics.

Instructions

Run SPSS linear regression. Specify a dependent variable and one or more predictors. Returns coefficients, R-squared, ANOVA table, and significance tests. 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>",
      "dependent": "<dependent>",
      "predictors": "<predictors>"
    },
    "name": "spss_regression"
  }
}

Input Schema

Name	Required	Default
`method`	No	ENTER
`dependent`	Yes
`file_path`	Yes
`predictors`	Yes
`include_diagnostics`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the IBM SPSS Statistics dependency and the statistical outputs (coefficients, R-squared, ANOVA, significance tests), but says nothing about whether files are modified, permissions, pagination, or error behavior.

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?

Four short sentences with the action front-loaded and no filler. Efficient, though the return-value sentence is somewhat redundant given an output schema exists.

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?

The existence of an output schema means the return-value details are redundant rather than necessary, and the missing coverage of 'method' and 'include_diagnostics' is a real gap for a 5-parameter statistical tool. Adequate but incomplete for its complexity.

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 5 parameters, so the description must compensate. It only clarifies 'dependent' and 'predictors' and never mentions 'method' (ENTER default), 'include_diagnostics', or 'file_path' semantics, leaving two parameters entirely undocumented.

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 (Run) and resource (SPSS linear regression) and identifies the required inputs (dependent variable, predictors). The word 'linear' implicitly distinguishes it from sibling spss_logistic_regression and spss_ordinal_regression, though it never names them 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?

No guidance on when to pick this over siblings like spss_logistic_regression, spss_anova, or spss_glm_univariate, nor on method selection or file prerequisites. The only usage note is the environment requirement.

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

Deploy Server