ChartAnt

Generate Boxplot Chart

generate_boxplot_chart

Read-only

Generate a boxplot chart to show data for statistical summaries among different categories, such as, comparing the distribution of data points across categories.

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": {
      "data": "<data>"
    },
    "name": "generate_boxplot_chart"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	Data for boxplot chart, such as, [{ category: '分类一', value: 10 }] or [{ category: '分类二', value: 20, group: '组别一' }].
`style`	No	Style configuration for the chart with a JSON object, optional.
`theme`	No	Set the theme for the chart, optional, default is 'default'.	default
`title`	No	Set the title of chart.
`width`	No	Set the width of chart, default is 600.
`height`	No	Set the height of chart, default is 400.
`axisXTitle`	No	Set the x-axis title of chart.
`axisYTitle`	No	Set the y-axis title of chart.
`brandTheme`	No	Name of a brand theme saved on the user's account (their colours and footer), only when the user asks for their theme. Or "colorblind" for colours that people with colour-vision deficiency can tell apart (anyone can use it).

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.2/5.0

Behavior2/5

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

The readOnlyHint annotation already establishes that this is a safe, non-destructive read operation. The description adds no behavioral context beyond that, such as what the tool returns, whether it renders immediately, or how it handles the provided data.

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?

The description is a single front-loaded sentence with no wasted preamble. The phrasing 'such as, comparing' is slightly awkward, but it remains concise and readable.

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?

For a chart-generation tool with a fully documented schema and a readOnly annotation, the description covers the essential purpose. However, it leaves out return behavior and does not help an agent choose between this and closely related distribution chart siblings.

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 100%, so all nine parameters are already documented in the schema, including the nested data and style objects. The description adds no parameter-level meaning beyond what the schema provides, which is the expected baseline here.

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 states a specific verb and resource: generate a boxplot chart for statistical summaries across categories. This is clear enough to distinguish it from most siblings, but it does not explicitly differentiate boxplot from closely related distribution charts such as violin or histogram.

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?

It gives an implied usage context, comparing distributions across categories, but does not state when to prefer a boxplot over a violin chart or histogram. No explicit exclusions or alternative-selection guidance is provided.

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

All ChartAnt tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?