No user-submitted related servers found.
Scored across 18 tools
The list_/get_ pairs for each entity are clearly distinct, and the search tool is explicitly scoped as cross-entity text search. Minor overlap exists because search_seqcode can return names, genomes, etc. that also have dedicated list tools, and list_type_genomes is a specialized subset of list_genomes/list_names, but descriptions clarify the boundaries.
All tools follow a predictable snake_case verb_noun pattern: list_publications/get_publication, list_names/get_name, etc. The few non-paired tools (list_type_genomes, search_seqcode, check_api_status) still conform to the same style. No mixed conventions or confusing variations.
With 18 tools, the set is slightly above the ideal 3-15 range, but the count is justified by the registry's breadth: eight entity types each need a list and get operation, plus search and status checks. No tool feels redundant or purely filler.
The server provides comprehensive read-only coverage for names, genomes, publications, authors, journals, subjects, and registers via list+get pairs. However, strains only have get_strain without a list_strains, limiting discoverability, and type genomes lack a dedicated get tool (though get_genome covers them). These are minor gaps for a read-only registry API.