Scored across 24 tools
Most tools target distinct resource+action pairs, and the match-level variants are carefully scoped by data family (score, events, odds, analysis, statistics). However, get_upcoming_matches and get_fixtures both list future matches, and get_match already exposes market/analysis data that dedicated odds/analysis tools also cover, so a couple of boundaries require careful reading.
All tools use lowercase snake_case with a consistent get_/search_/check_ prefix, and resources are named predictably (get_match, get_match_score, search_tournaments). The only mild deviations are get_h2h and check_api_status, but they still fit the overall pattern.
24 tools is on the heavy side and exceeds the typical well-scoped range, with some near-duplicate listing endpoints (upcoming vs fixtures) and several niche data families (archive, charting, odds/analysis). At the same time, each tool maps to a distinct data family and none feels purely redundant, so the count is heavy but not bloated.
The surface covers live scores, fixtures/results, players, tournaments, rankings, archive history, charting, odds, and analysis, which is unusually broad for a read-only API. Gaps are minor workflow issues: there is no tournament-id-based match/results listing, and historical/charting searches return ids that the career and H2H tools cannot directly consume since they take names.