Extract-Antv-Topic
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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, topic extraction, and intent analysis, while query_antv_document focuses on retrieving documentation and solutions. Their descriptions explicitly differentiate their roles, with no overlap in functionality.
Both tools follow a consistent verb_noun naming pattern (extract_antv_topic and query_antv_document), using snake_case throughout. The naming clearly reflects their respective actions and domain, with no deviations in style.
With only two tools, the server feels thin for its broad scope covering multiple AntV libraries and diverse use cases (implementation, debugging, learning, etc.). While the tools are well-defined, a more comprehensive set might better support the domain's complexity.
The tool set is severely incomplete for the AntV visualization domain. It lacks essential operations like code generation, library installation/management, configuration updates, or direct execution of visualization tasks. The two tools only cover preprocessing and documentation retrieval, leaving significant gaps for practical agent workflows.