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

echart-mcp-view

by SpenserCai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Open Sankey chart app

echart_mcp_view_open_sankey
Read-only

Create a Sankey diagram to visualize source-target flows with weighted links. Accepts node/link data or relational rows and maps fields for custom encoding.

Instructions

Open a focused Sankey MCP App for source-target flows with weighted links. 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_sankey"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoNodes/links or relation rows.
titleNoChart title.
advancedNoRenderer and safe option patch.
encodingNoRelation row mapping.
subtitleNoChart subtitle.
interactionNoBasic interactions.
presentationNoSankey presentation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, which the description does not contradict (opens an app, not modifying data). The description adds context about 'focused app' and 'safe option patch', but overall behavioral disclosure is adequate without redundancy.

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 concise, consisting of two sentences that front-load the main purpose and then provide quick usage hints. Every sentence adds value without unnecessary detail, making it efficient for an AI agent.

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 tool has 7 parameters with nested objects and no output schema, the description covers basic purpose and data formats but lacks details about expected behavior, return values, or limitations. It is minimally adequate but not fully comprehensive for the complexity.

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 100%, so baseline is 3. The description adds a high-level summary ('data holds rows, tree, or nodes/links; encoding maps fields') that provides some context beyond the schema, but it does not significantly enhance understanding of individual parameters like advanced or interaction.

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 opens a Sankey MCP App for source-target flows with weighted links, using specific verbs and resources. It distinguishes from sibling tools (other chart types) by explicitly naming the Sankey chart type and describing its data structures (rows, tree, nodes/links).

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 Sankey diagrams but does not explicitly state when to use this tool vs alternatives (e.g., graph, treemap). No 'when not to use' or comparison to siblings is provided, leaving the agent to infer from context.

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