ChartAnt

Generate Histogram Chart

generate_histogram_chart

Read-only

Generate a histogram chart to show the frequency of data points within a certain range. It can observe data distribution, such as, normal and skewed distributions, and identify data concentration areas and extreme points.

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

Input Schema

Name	Required	Description	Default
`data`	Yes	Data for histogram chart, it should be an array of numbers, such as, [78, 88, 60, 100, 95].
`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.
`binNumber`	No	Number of intervals to define the number of intervals in a histogram, when not specified, a built-in value will be used.
`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.4/5.0

Behavior3/5

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

readOnlyHint=true already signals a safe, non-mutating operation, so the description need not restate safety. It adds interpretive context about what the chart reveals but says nothing about the return form (image, URL, chart id), rendering cost, or how defaults for binNumber are chosen.

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?

Two sentences, front-loaded with the verb and artifact, and the second sentence earns its place by conveying analytic use cases. There is mild redundancy in the enumerated distribution examples but no filler.

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?

With 10 parameters, a nested style object, and no output schema, the definition leaves the response shape unexplained, which matters for a chart-rendering tool. The input side is fully covered by the schema, so the gap is limited to output and rendering behavior.

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%, including maxLength on brandTheme and enum semantics for theme and texture, so the schema carries the parameter burden. The description adds no additional meaning about binNumber behavior or style/theme interaction beyond what is already documented.

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 names a specific verb and artifact ('Generate a histogram chart') and scopes it to showing 'the frequency of data points within a certain range', which distinguishes it semantically from adjacent chart siblings like bar or scatter. It stops short of naming any sibling chart type 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?

It gives implied usage guidance by naming analytic goals (observing normal/skewed distributions, concentration areas, extreme points), which tells an agent when a histogram is the right lens. It never states when another chart type is preferable or what makes data unsuitable for a histogram.

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?