Read-only, structured access to a Git repository's history — as an MCP server and a CLI.
gitlore demonstrates solid fundamentals: all 7 tools have clear verb-noun names (search_commits, file_history, blame, churn, contributors, commit_detail, what_changed_between) and substantive descriptions (avg 120 chars). Input schemas are complete with proper types, descriptions, and constraints (min/max on limits, required flags). However, output schemas are not documented in the visible code, the tool definitions show input only. Error handling is present in the code (UnsafeArgumentError validation) but not surfaced in tool descriptions. No tool annotations (readOnlyHint, idempotentHint) despite all being read-only operations. Parameter descriptions are good but could be more prescriptive about format/constraints (e.g., date format for 'since'/'until').
Attribute each line of a file to the commit that last changed it, with that commit's subject. Use a line range for a specific passage.
Rank files by how often they change. High-churn files are where bugs and unclear ownership tend to concentrate.
One commit in full: its message, and every file it touched with line counts.
Who has worked on the repository or a path, and the bus factor — the fewest people accounting for over half of all commits.
Commits that touched a file, following it back through renames. Prefer this over search_commits when you have a specific path.
Search commit messages, optionally filtered by author, date range, or path.
Output schemas not documented. Tool definitions show input schemas only; return types are inferred from code (CommitPage, BlameResult, ChurnReport, etc.) but not declared in tool metadata. LLMs cannot plan downstream operations without knowing what fields to expect.
No tool annotations despite all tools being read-only. Missing readOnlyHint annotation on all 7 tools. This prevents clients from optimizing caching, retry logic, and safety checks for idempotent operations.
Date parameter format not specified. 'since' and 'until' accept git date formats ('3 months ago', ISO 8601, etc.) but descriptions do not clarify accepted formats. LLMs may pass invalid formats.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
Summarise what changed between two refs, without the full patch text.
Error handling not surfaced in tool descriptions. Code validates inputs (UnsafeArgumentError for null bytes, length limits, line ranges) but tool descriptions do not explain what errors are possible or how to recover. LLMs cannot self-correct on validation failures.
Pagination guidance incomplete. Tools return 'truncated' boolean but descriptions do not explain how to fetch next page (e.g., no offset/cursor parameter visible). Users cannot iterate through large result sets.