No user-submitted related servers found.
Scored across 3 tools
The tools have significant overlap in purpose, making them hard to distinguish. Both get_repository_overview and get_repository_stats appear to provide repository-level statistics, with get_repository_stats explicitly mentioning 'commits, authors, branches, and code changes' while get_repository_overview mentions 'stats, top contributors, and recent activity'—these descriptions suggest substantial redundancy. The only clearly distinct tool is get_author_stats, which focuses on contributor-level data.
All tool names follow a consistent verb_noun pattern using snake_case (get_author_stats, get_repository_overview, get_repository_stats). The naming is predictable and readable, with 'get' as the verb and descriptive nouns, showing no deviations in style or convention.
With only 3 tools, the server feels thin for a 'Git Analytics' domain, which typically involves more granular operations like trend analysis, commit filtering, or branch comparisons. While 3 tools can be appropriate for a minimal scope, the overlapping descriptions suggest this might be under-scoped, lacking depth in analytical capabilities.
The tool set is severely incomplete for a Git analytics server. It only provides 'get' operations for statistics, with no tools for filtering, comparing, trending, or analyzing specific aspects like code churn, hot spots, or temporal patterns. This limits agents to basic retrieval without supporting deeper analytical workflows, creating significant gaps in functionality.