No user-submitted related servers found.
Scored across 7 tools
The seven tools split cleanly by resource and action: search_works vs search_people, get_work vs list_work_files, get_person vs list_person_works, and the descriptions explicitly contrast the paired ones ('This reads the person; list_person_works reads what they wrote'). The only soft boundary is between browse_category and list_person_works, which share the same category-reading mechanics but differ by facet type (genre/key/instrumentation vs person).
Every name follows a strict verb_noun pattern (search_*, get_*, list_*_*, browse_*) in snake_case with no deviations. The verb choice also carries meaning: get_ for single-entity reads, list_ for paged collections, search_ for queries.
Seven tools is well-scoped for a read-only music library: two searches, two entity readers, two paged listers and one category browser. No tool is redundant, and nothing obviously needed is crammed in.
The surface covers the whole read lifecycle: discovery via search, entity detail via get_work/get_person, and inventory via list_work_files/list_person_works/browse_category, with pagination and section filtering documented. The gap is category discovery: browse_category demands facet names that only come back from get_work, so there is no way to enumerate genres, keys or instrumentations from a cold start.