Skip to main content
Glama
Sign In
spss-studio-mcp

spss-studio-mcp

by CongJyu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Spss Chart Area

spss_chart_area

Export publication-ready area charts of a y variable against time or ordinal x as PNG/TIFF using GGRAPH and OMS.

Instructions

Export a publication-ready area chart (PNG/TIFF) of y against a time/ordinal x variable, via GGRAPH + OMS.

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": {
      "x": "<x>",
      "y": "<y>"
    },
    "name": "spss_chart_area"
  }
}

Input Schema

NameRequiredDescriptionDefault
xYes
yYes
dpiNo
titleNo
x_labelNo
y_labelNo
width_pxNo
data_fileNo
height_pxNo
image_formatNoPNG

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/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 behavioral burden. It discloses that the operation exports a file and the underlying mechanism (GGRAPH + OMS), but does not state where the file is written, whether it requires an open/loaded dataset, whether it mutates state, or required permissions. The PNG/TIFF disclosure is already redundant with the image_format enum in the schema.

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?

A single front-loaded sentence with the verb and resource first and zero wasted words. Tightly sized given the absence of annotations.

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 no explanation, and the description covers chart type, axis semantics, and output format. However, for a 10-parameter chart-generation tool it omits the file destination, dataset prerequisites, and any parameter detail, leaving it only minimally complete.

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

Parameters3/5

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

Schema description coverage is 0% across 10 parameters, so the description must compensate. It adds genuine meaning for the two required params by specifying x as time/ordinal and y as the plotted value, but leaves the other eight (dpi, title, x_label, y_label, width_px, height_px, data_file, image_format) completely 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?

States a specific verb (Export) and resource (area chart) and pins the semantics of the two axes as 'y against a time/ordinal x variable'. This cleanly distinguishes it from the many sibling chart tools (line, bar, scatter, boxplot) by chart type without needing to open a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the chart type: an agent can infer 'use this when you want an area chart'. There is no explicit when-to-use, no prerequisites (e.g., active dataset required), and no routing versus similar siblings like spss_chart_line or spss_chart_bar.

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

Deploy Server

Other Tools