spss-studio-mcp

Overview Schema Source Related Servers Discussions Admin

Spss Chart Bar Error

spss_chart_bar_error

Generate publication-ready bar charts of category means with confidence-interval error bars, exported as PNG or TIFF files for statistical reporting.

Instructions

Export a publication-ready bar chart of category means with confidence-interval error bars (PNG/TIFF) 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": {
      "category": "<category>",
      "value": "<value>"
    },
    "name": "spss_chart_bar_error"
  }
}

Input Schema

Name	Required	Default
`ci`	No
`dpi`	No
`title`	No
`value`	Yes
`x_label`	No
`y_label`	No
`category`	Yes
`width_px`	No
`data_file`	No
`height_px`	No
`image_format`	No	PNG

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 12, 2026

TDQS

C2.7/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. It says 'Export' and '(PNG/TIFF)' but never states where the file is written, whether an existing file is overwritten, whether a data file must already be loaded, or what permissions/session state are needed. 'GGRAPH + OMS' is an implementation detail, not agent-useful behavior.

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?

A single efficient sentence with the key noun phrase front-loaded. No filler, though at only one sentence for an 11-parameter tool it is under-informative rather than over-long.

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-value explanation is not required, but with 11 parameters, 0% schema coverage, no annotations, and multiple look-alike sibling chart tools, a single sentence leaves the agent without enough to call it correctly or safely.

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 11 parameters, so the description must compensate. It only implicitly touches category/value (means), ci (error bars), and image_format (PNG/TIFF); the other seven parameters (dpi, title, labels, width_px, height_px, data_file) are undocumented anywhere.

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 gives a specific verb (Export) and a precisely qualified resource: a bar chart of category means with confidence-interval error bars, in PNG/TIFF. This meaningfully distinguishes it from plain spss_chart_bar and spss_chart_errorbar without naming them explicitly.

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 statement of when to choose this tool over the sibling charts (spss_chart_bar, spss_chart_errorbar, spss_chart_boxplot). No prerequisites, no mention of data_file requirements, and no indication of what kind of input data is expected.

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

Deploy Server