spss-studio-mcp

Overview Schema Source Related Servers Discussions Admin

Spss Descriptives

spss_descriptives

Run SPSS DESCRIPTIVES for numeric variables to return N, mean, standard deviation, min, max, and optional statistics; requires IBM SPSS Statistics.

Instructions

Run SPSS DESCRIPTIVES for numeric variables. Returns N, mean, std deviation, min, max, and optional statistics. 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_descriptives"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes
`variables`	Yes
`statistics`	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 must carry behavioral disclosure and does add real value: it lists the returned statistics and flags that IBM SPSS Statistics must be installed. It does not cover error behavior, how missing values or non-numeric variables are handled, or whether the call mutates state.

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?

Two compact sentences with the action and scope front-loaded, then output and the environment prerequisite. No filler, though the return-value listing partially duplicates the output schema.

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?

An output schema exists, so return values need not be restated, and the environment prerequisite is a useful addition. However, with three undocumented parameters and no annotations, the definition leaves gaps an agent would need to resolve before calling.

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 three parameters. The description hints at the 'statistics' parameter being optional and mentions numeric variables, but 'file_path' (a required parameter) is never explained and no value/format guidance is given for any parameter.

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 DESCRIPTIVES') scoped to 'numeric variables', which helps an agent distinguish it from frequency/crosstab procedures. It stops short of explicitly naming sibling alternatives like spss_frequencies or spss_file_summary, so differentiation relies on inference.

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 phrase 'for numeric variables' implies when the tool applies, but there is no explicit when-to-use versus alternatives such as spss_frequencies or spss_file_summary, and no prerequisites about data state. An agent must infer the routing decision.

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

Deploy Server