No user-submitted related servers found.
Scored across 59 tools
The vast majority of tools target a clearly distinct entity+action (get_artist, get_similar_tracks, scrobble_tracks, love_track). A few pairs are subtly distinguishable only by a naming suffix convention: get_album_tags (one user's tags) vs get_album_top_tags (community tags), and get_top_tags vs get_chart_top_tags, which read as very similar. The consistent X_tags/X_top_tags scheme mostly saves these from confusion.
Names follow a predictable snake_case verb_noun pattern (get_*, search_*, add_*_tags, remove_*_tag, get_user_*, get_tag_*), which makes the surface scannable. Minor deviations exist, e.g. love_track/unlove_track and start_authentication/finish_authentication, and get_result_page breaks the domain prefix pattern.
59 tools is very heavy and sits at the extreme end; while each maps to a real Last.fm API endpoint, the count imposes a large selection burden on an agent. Many near-mirror families (four get_user_*_top, three get_user_weekly_*_chart, three get_tag_top_*, four get_*_tags) inflate the surface beyond what most tasks need.
Coverage is broad and faithful: artists, albums, tracks, tags, users, geo charts, auth lifecycle, scrobbling, loved tracks, weekly charts, corrections, and a paging helper. Minor gaps remain, such as no library-track or library-album listings to complement get_library_artists, and tag weekly charts provide only the range list without the actual chart data.