highchart-mcp-server

render_chart

Render a chart using any valid Highcharts configuration object. The server validates structure and passes through all options to generate the chart.

Instructions

Render a chart from a full Highcharts configuration object. Accepts any valid Highcharts Options — the server validates structure (chart.type, series) but passes all other options through to Highcharts.

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": {
      "chartOptions": "<chartOptions>"
    },
    "name": "render_chart"
  }
}

Input Schema

Name	Required	Description	Default
`chartOptions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that the server validates `chart.type` and `series` and passes other options through. However, it does not describe the return value, side effects, or any required authentication, leaving gaps for a mutation-like operation.

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 description is two sentences, front-loaded with the primary purpose. Every sentence provides essential information without redundancy or unnecessary words.

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?

Given the complexity of a nested object parameter and no output schema, the description covers input behavior well but omits return value details and potential constraints (e.g., output format, limits). More context would improve completeness.

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?

The description adds significant meaning beyond the raw schema by clarifying that the parameter accepts any valid Highcharts Options and that all properties are passed through. This compensates for the 0% schema description coverage.

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 clearly states 'Render a chart from a full Highcharts configuration object,' specifying the action and resource. It distinguishes from the sibling 'create_chart' by implying rendering versus creation, but does not explicitly differentiate usage scenarios.

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?

The description implies the tool is for rendering when a full Highcharts config is available, but it does not provide explicit guidance on when not to use it or how it compares to 'create_chart'. No exclusions or alternatives are mentioned.

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

Deploy Server