Darwin-owned AntV Charts

generate_bar_chart_from_csv

Read-only

Render a real PNG bar chart from supplied UTF-8 CSV. Select exact category and numeric value columns. At most 50 complete rows, 16 columns and 24 KiB UTF-8; no truncation, duplicate categories, numeric rounding or URL/file fetching. Uses Darwin-hosted AntV with its fixed public free renderer, no API key or payment.

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": {
      "csv": "<csv>",
      "categoryColumn": "<categoryColumn>",
      "valueColumn": "<valueColumn>"
    },
    "name": "generate_bar_chart_from_csv"
  }
}

Input Schema

Name	Required	Description	Default
`csv`	Yes
`style`	No
`theme`	No	Set the theme for the chart, optional, default is 'default'.	default
`title`	No
`width`	No
`height`	No
`axisXTitle`	No
`axisYTitle`	No
`valueColumn`	Yes
`categoryColumn`	Yes

Output Schema

Name	Required	Description	Default
`artifact`	Yes
`provenance`	Yes
`requestMetadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4/5.0

Behavior5/5

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

The description adds substantial behavioral detail beyond annotations: it specifies real PNG output, hard limits (50 rows, 16 columns, 24 KiB), no truncation, no duplicate categories, no numeric rounding, and no URL/file fetching. It also discloses the external Darwin-hosted AntV renderer and that no API key or payment is required, which is important for an openWorldHint tool.

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

Conciseness5/5

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

The core action is front-loaded in the first sentence, followed by validation constraints and renderer details. The paragraph is dense but every sentence carries operational information, with no filler or repetition.

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?

Given the tool's complexity, the description covers the most important call-shaping details: CSV constraints, required columns, output format, failure modes, and external renderer behavior. An output schema exists, so return shape need not be explained, but optional styling and layout parameters remain mostly documented only by the schema.

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 only 10%, so the description must compensate. It usefully explains the required categoryColumn and valueColumn roles and gives CSV size/shape limits, but it does not add meaning for the style, palette, texture, backgroundColor, title, width, height, axisXTitle, or axisYTitle parameters.

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: render a PNG bar chart from UTF-8 CSV. It clearly identifies the CSV source and required category/value columns, but it does not explicitly distinguish this tool from sibling generate_bar_chart or explain when that sibling would be preferred.

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 CSV-specific constraints and required columns, so an agent can infer this is the CSV-input bar chart variant. However, there is no explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative such as generate_bar_chart for non-CSV inputs.

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

All Darwin-owned AntV Charts 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?