Server provides 4 read-only Git tools with basic structure. Tool naming follows verb_noun pattern (get_*, git-*) and is reasonably clear. Descriptions are minimal but present (10-50 chars, below the 194 baseline median). Input schemas are partially defined: two tools have no parameters, two have a single 'ancestor' string param with description. Output schemas are not documented in the visible code, only internal formatting functions exist. No error handling guidance for LLMs. Missing parameter constraints (enums, ranges, format specs). No tool annotations (readOnlyHint present via Risk field but not in MCP schema). The server is functional but falls short of production-grade tool design. Common issue: descriptions too brief to guide LLM selection (e.g., 'Get diff results...' does not explain WHEN to use this vs. git-unstaged-diff).

• Expand tool descriptions to 100-200 chars. For git-diff: 'Get unified diff between a specified ancestor commit (or branch) and HEAD. Shows all file changes. Use git-cached-diff to see staged-only changes; git-unstaged-diff for working-tree changes.' This disambiguates from similar tools.
• Document output schemas for all tools. Example: 'Returns a list of diff objects, each with keys: a_path (source path), b_path (target path), diff (unified diff string). If no changes, returns empty list.'
• Add parameter descriptions and constraints. For 'ancestor' param: 'A commit SHA, branch name (e.g., main, develop), or tag. Must exist in the repository. If invalid, git-commit-messages will raise an error, verify with git log.'
• Add error handling guidance to descriptions. Example: 'If ancestor commit not found, returns: ValueError: Error executing Git command: <git error>. Call with a valid branch name (e.g., main) or verify the commit SHA exists.'
• Add readOnlyHint annotation to all four tools in MCP schema registration. Agents need to know these tools are safe to call without consequences.
• For git-cached-diff and git-unstaged-diff, update descriptions to clarify they require no parameters: 'Returns staged changes (HEAD vs index) without requiring an ancestor parameter. Use this to preview changes before committing.'
• Consider adding a limit parameter to handle large repos gracefully. Document max size: 'Large diffs may exceed context limits. If diff is > 100KB, results are truncated, use ancestor parameter to narrow the range.'

Inferred effective spec: 2025-06-18+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry