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

echart-mcp-view

by SpenserCai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Open Radar chart app

echart_mcp_view_open_radar
Read-only

Display multi-dimensional profile comparisons using a radar chart. Map fields for name, category, and numeric values from tabular data.

Instructions

Open a focused radar chart MCP App for multi-dimensional profile comparisons. 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_radar"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataNoTabular rows.
titleNoChart title.
advancedNoRenderer and safe option patch.
encodingNoRadar field mapping.
subtitleNoChart subtitle.
interactionNoItem interactions.
presentationNoRadar presentation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, so the description does not need to restate that. The description adds no further behavioral context beyond 'Open', which is consistent. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short (two sentences) but the second sentence is inaccurate regarding data types and could be more precise. It conveys the core purpose but includes misleading information.

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

Completeness2/5

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

Given the complexity (7 parameters, nested objects) and no output schema, the description is insufficient. It omits details about how data should be structured, what the app does, and return behavior. The incorrect mention of tree/nodes/links further reduces 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 schema covers 100% of parameters with descriptions. The description adds value by summarizing how to use top-level parameters (title, subtitle, data, encoding), providing a high-level guide that complements the schema.

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 it opens a radar chart app for multi-dimensional profile comparisons, which differentiates it from sibling tools for other chart types. However, it incorrectly mentions that data can be a tree or nodes/links, which contradicts the input schema that only supports rows.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or use cases. It simply states what the tool does without comparing to sibling tools.

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