spss-studio-mcp

Overview Schema Source Related Servers Discussions Admin

Spss Compute Scale Score

spss_compute_scale_score

Compute a SUM or MEAN scale score from multiple item variables for SPSS data, with optional reverse coding and a minimum valid item count.

Instructions

Compute a scale score (SUM or MEAN) from multiple item variables, with optional reverse coding and minimum valid item count. 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>",
      "new_variable": "<new_variable>",
      "items": "<items>"
    },
    "name": "spss_compute_scale_score"
  }
}

Input Schema

Name	Required	Default
`items`	Yes
`method`	No	mean
`file_path`	Yes
`min_valid`	No
`reverse_max`	No
`reverse_min`	No
`new_variable`	Yes
`reverse_items`	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 of behavioral disclosure. It mentions the SPSS installation requirement, but does not say whether the tool modifies the source file, writes a new variable to disk, or how reverse coding and min_valid interact with the computation. Side effects and failure behavior are left unstated.

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?

The description is two sentences with no wasted words, front-loading the core action before the prerequisite. Both sentences earn their place and the text is easy to scan.

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?

Given 8 parameters, 0% schema description coverage, no annotations, and a composite-scoring operation that likely mutates data, the description is too thin. Because an output schema exists, return values need not be explained, but critical operational details about parameter meaning and side effects are missing.

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%, so the description must compensate, but it only clarifies method (SUM or MEAN), reverse coding, and minimum valid item count. It does not explain file_path, new_variable, items, reverse_items, or the reverse_min/reverse_max pair, leaving most of the 8 parameters 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?

The description states a specific verb and resource ('Compute a scale score (SUM or MEAN) from multiple item variables') and adds scope details like reverse coding and minimum valid item count. It does not explicitly distinguish itself from siblings such as spss_reliability_alpha or spss_run_syntax, so it falls short of a 5.

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?

There is no explicit when-to-use guidance, no exclusions, and no named alternatives. The only contextual note is the prerequisite that IBM SPSS Statistics must be installed, which is not usage guidance. An agent must infer when this tool is preferred over other SPSS procedures.

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

Deploy Server