No user-submitted related servers found.
Scored across 35 tools
Most tools map cleanly to a specific KEGG entry type plus action, so an agent can generally distinguish search_compounds, search_drugs, get_pathway_genes, get_pathway_reactions, etc. Minor overlap exists between find_related_entries and convert_identifiers/get_gene_orthologs, and between draw_pathway_map and render_pathway_ascii in the sense of pathway visualization, but the descriptions clarify output modes.
The set is overwhelmingly snake_case and follows predictable patterns such as search_<db>, get_<db>_info, get_pathway_<subresource>, and list_organisms. A few one-off verbs (draw_pathway_map, render_pathway_ascii, batch_entry_lookup, convert_identifiers) are semantically appropriate but keep it from being perfectly uniform.
KEGG is a very broad domain with many entry types, so 35 tools is defensible, but it is still heavy for an agent to navigate. Several search/get pairs could potentially be consolidated or generalized, making the surface borderline rather than well-scoped.
The server covers the major KEGG databases with search, retrieval, linking, batch lookup, identifier conversion, and pathway visualization. Gaps are modest: there is no dedicated genome-info retrieval beyond list_organisms/get_database_info, and cross-database traversal relies heavily on find_related_entries rather than more specific linked-resource tools.