ChartAnt

Dashboard image

generate_dashboard

Read-only

Combine KPI cards, charts, maps and short notes into ONE image, in rows (1-4 rows, 1-4 panels per row, at most 8 panels). For weekly email updates, Slack posts, client reports and slides. Each panel is a chart definition with its 'type' (kpi, line, column, bar, pie, area, country-map, world-map, county-map, small-multiples, or note for a sentence of text: {type:'note', text}). Typical: a row of KPI cards, then a trend chart beside a map or a top-10 bar chart, then a note with the takeaway.

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": {
      "rows": "<rows>"
    },
    "name": "generate_dashboard"
  }
}

Input Schema

Name	Required	Description
`rows`	Yes	Rows of panels, top to bottom; each panel like {"type":"line","title":"…","data":[…]}.
`title`	No
`width`	No	Image width in pixels (default 1200).
`subtitle`	No
`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

A4.5/5.0

Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries the real load and does add hard behavioral constraints: 1-4 rows, 1-4 panels per row, at most 8 panels total. It stops short of describing the returned artifact (image URL vs. base64, rendering latency), which an agent would want to know.

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?

Front-loaded with the core action and size limits, then use cases, then a worked layout example. Three sentences with little waste, though the type enumeration and the sample layout make it denser than strictly necessary.

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

Completeness5/5

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

A five-parameter composite-rendering tool with no output schema needs layout rules, panel vocabulary, and purpose context — all present. No output schema means the return value needn't be explained, and the required 'rows' parameter is fully demystified.

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

Parameters5/5

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

At 60% schema coverage the description compensates substantially: the schema leaves panel objects as unconstrained additionalProperties, and the description supplies the actual panel vocabulary (kpi, line, column, bar, pie, area, country-map, world-map, county-map, small-multiples, note) plus the note shape {type:'note', text}. It also explains the rows-of-panels nesting semantics and clarifies brandTheme's 'colorblind' escape hatch.

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?

Opens with a specific verb and composite resource: 'Combine KPI cards, charts, maps and short notes into ONE image, in rows'. The word 'ONE' plus the multi-panel framing immediately separates it from the single-chart siblings like generate_line_chart or generate_kpi_card.

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?

Gives concrete destination contexts (weekly email updates, Slack posts, client reports, slides) and a 'typical' layout recipe, which tells the agent what this is for. It never explicitly says 'use a single-chart tool instead when you only need one panel', so the routing back to siblings is left implicit.

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?