echarts-mcp

Validate ECharts option

validate_echart_option

Validate ECharts options against echarts 6.1.0 without rendering. Returns errors that would break a render and warnings for likely mistakes.

Instructions

Dry-run structural and semantic validation of an ECharts option against echarts@6.1.0 without rendering. Returns errors (would break a render) and warnings (likely mistakes).

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": {
      "option": "<option>"
    },
    "name": "validate_echart_option"
  }
}

Input Schema

Name	Required	Description	Default
`option`	Yes	The ECharts option object to validate.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Aug 17, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly states it is a dry-run (no rendering) and returns errors and warnings, which are meaningful behavioral traits. It does not detail edge cases or side effects, but the core behavior is transparent.

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 long, front-loaded with the key action ('Dry-run structural and semantic validation') and includes the return value summary. Every word contributes to the user's understanding with no fluff.

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 single-parameter tool with no annotations and no output schema, the description effectively covers the tool's purpose, behavioral constraints, and return semantics. It could be more complete by listing example validation rules or the exact return shape, but it is largely sufficient for an AI agent to decide when and how to invoke it.

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?

The schema already fully describes the only parameter 'option' with a clear description, so baseline is 3. The tool description adds the version context (echarts@6.1.0) and validation scope (structural/semantic) but does not add additional parameter-level meaning beyond the schema.

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?

The description clearly states the tool performs 'structural and semantic validation of an ECharts option against echarts@6.1.0 without rendering.' It uses a specific verb ('validates') and resource ('ECharts option'), and the 'without rendering' clause distinguishes it from the sibling render_echart tool.

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 usage context by noting 'without rendering' and 'dry-run', suggesting it is the safe pre-render check. However, it never explicitly mentions alternative tools or provides when-to-use vs. when-not-to-use guidance relative to siblings render_echart and list_chart_types.

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

Deploy Server