spss-studio-mcp

Overview Schema Source Related Servers Discussions Admin

Spss Structured Result

spss_structured_result

Execute SPSS syntax to obtain structured JSON output with tables, summary statistics, and warnings for t-test, ANOVA, correlation, and regression analyses.

Instructions

Run SPSS syntax and return a unified structured result as JSON: {markdown, json: {tables, summary}, files, warnings}. The summary extracts key statistics (t/F/r/B/p) for t-test, ANOVA, correlation, regression, descriptives and frequencies.

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": {
      "syntax": "<syntax>"
    },
    "name": "spss_structured_result"
  }
}

Input Schema

Name	Required	Description	Default
`syntax`	Yes
`data_file`	No
`select_if`	No
`filter_variable`	No
`save_syntax_file`	No
`save_viewer_output`	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.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the return structure and summary behavior, which is useful, but does not state execution side effects, permission requirements, data-modification risk, or what the save flags do.

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 sentences, both load-bearing, with the core action and output shape front-loaded. The second sentence efficiently details the summary extraction without filler.

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 fully explained, and the description does cover the return envelope. But with six parameters, no annotations, no parameter descriptions, and no usage guidance relative to many siblings, the description is materially incomplete for correct invocation.

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

Parameters1/5

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

Six parameters exist and schema description coverage is 0%, but the description explains none of them. It says 'Run SPSS syntax' which only restates the required 'syntax' parameter name, and adds no meaning for data_file, select_if, filter_variable, save_syntax_file, or save_viewer_output.

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 syntax and return a unified structured result. The output shape and summary-statistic extraction are made explicit, which helps identify it as a structured-output variant. However, it does not explicitly distinguish itself from the sibling spss_run_syntax tool.

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?

Provides no when-to-use guidance, no exclusions, and no named alternatives. An agent cannot tell from the description when to choose this tool over spss_run_syntax or the many analysis-specific siblings.

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

Deploy Server