Skip to main content
Glama
Sign In
echart-mcp-view

echart-mcp-view

by SpenserCai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Open Mixed chart app

echart_mcp_view_open_mixed
Read-only

Opens a mixed chart combining bar and line series on shared axes. Configure data, encoding, and series settings for dual visualization.

Instructions

Open a focused mixed chart MCP App for combined bar and line series on shared axes. Use top-level title/subtitle; data holds rows, tree, or nodes/links; encoding maps fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "echart_mcp_view_open_mixed"
  }
}

Input Schema

NameRequiredDescriptionDefault
axesNoMixed axis mapping.
dataNoTabular rows.
titleNoChart title.
seriesNoMixed series list.
advancedNoRenderer and safe option patch.
encodingNoMixed field mapping.
subtitleNoChart subtitle.
interactionNoCartesian interactions.
presentationNoMixed presentation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds context about data formats but does not disclose additional behavioral traits beyond what annotations provide, so it offers moderate added value.

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-loading the core purpose and then summarizing key inputs. Every sentence conveys useful information without redundancy.

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 9 parameters, nested objects, and no output schema, the description only covers title/subtitle, data formats, and encoding, missing axes, series, interaction, presentation, and advanced options. However, thorough schema descriptions compensate partially.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by stating data can hold 'rows, tree, or nodes/links' and that encoding 'maps fields', which goes slightly beyond the schema descriptions.

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 verb 'Open', the resource 'focused mixed chart MCP App', and specifies the unique capability 'combined bar and line series on shared axes', which distinguishes it from sibling chart tools.

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 for mixed bar-line charts but provides no explicit guidance on when to use this tool versus alternatives (e.g., open_bar, open_line) or when not to use it.

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

Deploy Server

Other Tools