Scored across 39 tools
The set contains several overlapping clusters, especially merge request notes/discussions (get_merge_request_note, get_merge_request_notes, get_merge_request_discussion, mr_discussions) and diffs (get_merge_request_diffs, list_merge_request_diffs, get_merge_request_file_diff, list_merge_request_changed_files). Descriptions do cross-reference each other to reduce confusion, but the boundaries remain nuanced and an agent could easily misselect.
Most tools follow a clear snake_case verb_noun pattern (e.g., create_issue, list_merge_requests, get_commit_diff). A few deviations exist, such as whoami, my_issues, mr_discussions, and health_check, but overall the convention is readable and predictable.
With 39 exposed tools, the surface is much larger than the 3–15 range typically considered well-scoped. Many are highly granular, read-only variants (multiple diff and note getters) that inflate the count beyond what the core workflows require.
Core GitLab areas like issues, merge requests, projects, branches, commits, and files have read coverage plus some creation/update. However, key lifecycle operations are missing: no merge_merge_request, no branch or file creation/deletion, no project creation, no label management, and no CI/pipeline tools exposed. The discover_tools mechanism can activate more categories, but the current surface has notable gaps.