ChartAnt

Generate Dual Axes Chart

generate_dual_axes_chart

Read-only

Generate a dual axes chart which is a combination chart that integrates two different chart types, typically combining a bar chart with a line chart to display both the trend and comparison of data, such as, the trend of sales and profit over time.

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": {
      "categories": "<categories>",
      "series": "<series>"
    },
    "name": "generate_dual_axes_chart"
  }
}

Input Schema

Name	Required	Description	Default
`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.
`series`	Yes	Series for dual axes chart, such as, [{ type: 'column', data: [91.9, 99.1, 101.6, 114.4, 121], axisYTitle: '销售额' }, { type: 'line', data: [0.055, 0.06, 0.062, 0.07, 0.075], 'axisYTitle': '利润率' }].
`axisXTitle`	No	Set the x-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).
`categories`	Yes	Categories for dual axes chart, such as, ['2015', '2016', '2017'].

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a non-mutating generation call, so the description isn't obligated to cover safety. It adds useful framing about the dual-scale structure (quantities on one axis, ratios under 1 on the other appears only in the schema), but says nothing about what is produced or how series map to axes.

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 front-loaded sentence that defines the chart type before giving the use case. It is slightly padded ('which is a combination chart that integrates two different chart types' loosely repeats 'dual axes chart') but no sentence is wasted.

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 9-parameter tool with nested objects and no output schema, the description covers the conceptual model but omits what the call returns (image, URL, chart spec) and any constraints such as how many series can be supplied. Adequate but with a real gap around output expectations.

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 parameter including nested series/style fields is already documented with examples. The description adds no parameter-level meaning beyond what the schema provides, which is the expected baseline 3.

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+resource ('Generate a dual axes chart') and defines the artifact precisely as a combination chart integrating two chart types, typically bar + line. An agent can distinguish it from generate_bar_chart or generate_line_chart by the two-metric framing, though 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?

Usage is implied rather than stated: 'to display both the trend and comparison of data' hints at when this beats a single-type chart, and the sales/profit example anchors it. There is no explicit when-not guidance or routing to alternative single-axis chart tools.

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?