Local assistant for reconstructing the history and motivations of a Git repository using MCP tools and local LLM
Server provides 5 well-scoped Git analysis tools with complete input schemas and Italian descriptions. All tools are READ_ONLY and follow verb_noun naming (repositoryOverview, fileHistory, blameLines, searchHistory, inspectCommit). Schemas are properly typed with required fields marked. However, descriptions are brief (avg ~80 chars) and lack actionable context for LLM selection. No output schemas documented. Parameter descriptions are minimal, e.g., 'Percorso relativo del file nel repository' lacks format guidance or examples. No error handling guidance visible. Tool composition is sound (each does one thing), but descriptions don't explain WHEN to use each tool vs. alternatives or what downstream tools might need.
Attribuisce le righe di un file ai commit che le hanno introdotte
Mostra la storia di un file, incluse rinomine e patch rilevanti
Mostra metadati e patch completa di uno specifico commit
Restituisce identità, branch, stato e statistiche recenti del repository Git
Cerca commit il cui messaggio o contenuto modificato contiene un termine
Output schemas not documented. LLMs cannot plan downstream calls or extract required fields (e.g., commit hash, author, date). Responses are opaque.
Parameter descriptions lack format guidance and constraints. 'filePath' does not specify: relative vs. absolute, allowed characters, max length, or examples. 'query' in searchHistory does not explain: literal string vs. regex, case sensitivity, or max length.
Tool descriptions are too brief (avg 80 chars, baseline 194 chars) and lack WHEN/WHY context. 'Mostra la storia di un file' does not explain: when to call this vs. blameLines, what 'storia' includes (renames, patches, deletions), or what fields are returned.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
No error handling guidance. If a file path is invalid, commit hash not found, or query returns no results, LLM receives no recovery hint. Descriptions do not state prerequisites (e.g., 'requires valid Git repository').
Tool composition lacks chaining hints. If fileHistory returns a commit hash, does inspectCommit accept that hash? If searchHistory finds commits, what fields does it return to enable downstream calls? Responses must include IDs/references downstream tools accept.