Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Generate Violin Chart

generate_violin_chart
Read-only

Generate a violin 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_violin_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesData for violin chart, such as, [{ category: 'Category A', value: 10 }], when the data is grouped, the 'group' field is required, such as, [{ category: 'Category B', value: 20, group: 'Group A' }].
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.
axisXTitleNoSet the x-axis title of chart.
axisYTitleNoSet the y-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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and title, so the safety profile is known; the description adds little beyond it. It does not mention that a chart is rendered/persisted, whether versions are created (siblings list_chart_versions, restore_chart_version imply state), or output format, though it does flag the grouping requirement in the data schema.

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, compact sentence that front-loads the verb and purpose without wasted wording. The doubled comma and redundant 'such as,' phrasing are minor blemishes.

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 chart-generation tool with full schema coverage and a readOnly annotation, the description covers what the tool produces at a high level. It is somewhat thin on the data shape details and does not clarify theme/brandTheme interactions, but no output schema means the high-level summary is mostly sufficient.

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, including the nested data/group and style fields, are already documented in the schema. The description adds no extra parameter meaning such as axis assignment or group ordering, so the baseline of 3 applies.

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 violin chart') plus the visualization's purpose, comparing distributions across categories. It does not explicitly distinguish this from siblings like boxplot or histogram, which also show distributions, so sibling differentiation is missing.

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 by the phrase about comparing distribution of data points across categories, which hints at the right scenario. However, it never states when to prefer a violin chart over generate_boxplot_chart or generate_histogram_chart, and gives no exclusions or prerequisites.

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