Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Generate Dual Axes Chart

generate_dual_axes_chart
Read-onlyIdempotent

Draw a combined column and line chart with two y-axes, for two measures with different units over the same categories (revenue in € as columns, margin in % as a line). Give categories [..] and series [{type: 'column'|'line', data [numbers], axisYTitle?}]. Returns a hosted PNG link, a share page, alt text and editable PowerPoint/Excel links.

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

NameRequiredDescriptionDefault
styleNoStyle configuration for the chart with a JSON object, optional.
themeNoSet the theme for the chart, optional, default is 'default'.default
titleNoSet the title of chart.
widthNoSet the width of chart, default is 600.
heightNoSet the height of chart, default is 400.
seriesYesSeries 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': '利润率' }].
axisXTitleNoSet the x-axis title of chart.
brandThemeNoName 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).
categoriesYesCategories for dual axes chart, such as, ['2015', '2016', '2017'].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this as safe, idempotent and non-destructive, so the bar is lower. The description still adds genuinely useful behavior: it returns a hosted PNG link, a share page, alt text and editable PowerPoint/Excel links, which matters because there is no output schema. It does not mention auth, rate limits, or whether hosted artifacts expire.

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?

Three front-loaded sentences with no filler, ordered use case, input shape, then outputs. The bracketed shorthand '[..]' and 'data [numbers]' is slightly cryptic but compact, and it restates schema structure rather than adding to it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter nested tool with no output schema, the description covers the two required inputs, the distinguishing semantics, and the return artifacts, which are the essentials for correct invocation. Style, theme, width/height and brandTheme are left entirely to well-documented schema properties, which is a reasonable division but leaves the caller without any hint that brandTheme is conditional on user request.

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

Parameters4/5

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

Schema coverage is 100%, giving a baseline of 3. The description goes past that by naming the two required parameters (categories, series), sketching the series item shape with the type/axisYTitle keys, and explaining the semantic contract that the column series is quantities while the line series is ratios on a second scale.

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?

The description opens with a specific verb and resource combination: 'Draw a combined column and line chart with two y-axes'. The dual-axis combined form is unique among the generate_*_chart siblings, so an agent can distinguish it without opening any schema.

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

Usage Guidelines4/5

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

It states the selecting condition clearly: two measures with different units over the same categories, with a concrete revenue-as-columns / margin-as-line example. What is missing is any exclusion or pointer to alternatives, e.g. that a single-measure comparison should use generate_column_chart or generate_line_chart instead.

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

All ChartAnt toolsInspect
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