ChartAnt

Generate Bar Chart

generate_bar_chart

Read-only

Generate a horizontal bar chart to show data for numerical comparisons among different categories, such as, comparing categorical data and for horizontal comparisons.

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_bar_chart"
  }
}

Input Schema

Name	Required	Description	Default
`data`	Yes	Data for bar chart, such as, [{ category: '分类一', value: 10 }, { category: '分类二', value: 20 }], when grouping or stacking is needed for bar, the data should contain a `group` field, such as, when [{ category: '北京', value: 825, group: '油车' }, { category: '北京', value: 1000, group: '电车' }].
`group`	No	Whether grouping is enabled. When enabled, bar charts require a 'group' field in the data. When `group` is true, `stack` should be false.
`stack`	No	Whether stacking is enabled. When enabled, bar charts require a 'group' field in the data. When `stack` is true, `group` should be false.
`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.
`animated`	No	true for an animated GIF (bars grow, lines draw, pies sweep open) instead of a still PNG; for email, slides and chat posts. The first frame is the finished chart.
`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/5.0

Behavior2/5

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

Annotations only declare readOnlyHint=true; the description adds nothing beyond purpose. It never says what is produced (still PNG vs animated GIF), where it is stored, or that group/stack are mutually exclusive — all information the agent needs but which sits only in the schema's parameter text.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence is appropriately brief, but it is loosely structured: 'such as, comparing categorical data and for horizontal comparisons' is circular and repeats the opening clause instead of adding information.

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?

With 12 parameters, nested data objects, and no output schema, the description should at minimum indicate what the tool returns (an image, a URL, a chart id) and who renders it. It omits the return value entirely, leaving a significant gap for a complex tool.

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 every one of the 12 parameters is already documented in the schema, including the group/stack exclusivity and the data shape. The description adds no parameter meaning beyond that, which is the expected baseline when the schema carries the load.

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 (generate a horizontal bar chart) and names the analytical use case (numerical comparisons among categories). The 'horizontal' qualifier implicitly separates it from the vertical-bar column chart sibling, but no sibling is named explicitly.

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?

Provides usage context ('for numerical comparisons among different categories', 'horizontal comparisons') but the trailing phrase restates the same idea rather than extending it. No exclusions or pointers to alternative chart types (e.g., column chart for vertical, pie for part-to-whole) are given.

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?