Skip to main content
Glama

spss_graph_scatter

Create a bivariate scatterplot from an SPSS data file, plotting y against x with optional panel grouping to reveal relationships.

Instructions

Scatterplot: GRAPH /SCATTERPLOT(BIVAR)=y WITH x [BY panel]. Requires IBM SPSS Statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
file_pathYes
x_variableYes
y_variableYes
panel_variableNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Install Server

TDQS

B3.3/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 does disclose that IBM SPSS Statistics is required and reveals the exact syntax and optional paneling behavior. However, it does not describe side effects on files, output details, or any limitations.

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 extremely compact and front-loaded with the chart type. The SPSS syntax and software prerequisite each add useful information without redundant prose.

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?

Even with an output schema present, the definition lacks enough context for reliable invocation. The meaning of file_path is not specified, optional parameters are only implied by syntax, and there is no guidance on variable requirements or when to choose this tool over related analyses.

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 property coverage is 0%, so the description must compensate. It maps y_variable, x_variable, and panel_variable to positions in the SPSS syntax, but it says nothing about the required file_path or the optional title, leaving key parameters undocumented.

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

Purpose5/5

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

The description states this creates a scatterplot and gives the exact SPSS command structure, 'GRAPH /SCATTERPLOT(BIVAR)=y WITH x [BY panel]'. This clearly distinguishes it from sibling chart tools like histogram, boxplot, and bar.

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 description provides no explicit when-to-use or when-not-to-use guidance. It only notes the SPSS requirement and does not mention alternatives such as correlation or regression, nor when the optional BY panel parameter should be used.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rasitnarcicek/spss-mcp-extended'

If you have feedback or need assistance with the MCP directory API, please join our Discord server