Related Servers

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.