MCP Server AntV
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| extract_antv_topicA | AntV Intelligent Assistant Preprocessing Tool - Specifically designed to handle any user queries related to AntV visualization libraries. This tool is the first step in processing AntV technology stack issues, responsible for intelligently identifying, parsing, and structuring user visualization requirements. MANDATORY: Must be called for ANY new AntV-related queries, including simple questions. Always precedes query_antv_document tool. When to use this tool:
Key features:
|
| query_antv_documentA | AntV Context Retrieval Assistant - Fetches relevant documentation, code examples, and best practices from official AntV resources. Supports g2, g6, l7, x6, f2, s2, g, ava, adc libraries, and handles subtasks iterative queries. MANDATORY: Must be called for ANY AntV-related query (g2, g6, l7, x6, f2, s2, g, ava, adc), regardless of task complexity. No exceptions for simple tasks. When to use this tool:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: extract_antv_topic handles preprocessing, requirement parsing, and intent extraction, while query_antv_document focuses on retrieving documentation and solutions. Their mandatory sequencing (extract first, then query) reinforces this separation, eliminating any ambiguity about when to use each tool.
Both tools follow a consistent verb_noun pattern with snake_case naming: extract_antv_topic and query_antv_document. The naming clearly indicates their functions (extract vs. query) while maintaining domain specificity (antv_topic vs. antv_document), creating a predictable and readable convention throughout the set.
With only 2 tools, the server feels thin for covering the broad AntV visualization domain (9 libraries mentioned). While the tools logically separate preprocessing from retrieval, many visualization tasks might require additional operations like code generation, validation, or specific library interactions that aren't represented in this minimal set.
The tool surface is severely incomplete for the AntV visualization domain. While the tools cover preprocessing and documentation retrieval, there are significant gaps: no tools for actual code generation, chart rendering, data transformation, style modification, or error handling. Agents will hit dead ends when trying to implement solutions beyond documentation lookup.