Loading ToolBench
MCP server that generates professional standup messages from git commit history with date filtering
Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output structure. get_commits has a time_period enum but lacks description for it; generate_standup_message has incomplete parameter descriptions (hash, message, author lack descriptions). Neither tool documents output schema explicitly. Descriptions are present but generic (194-char baseline suggests room for improvement). No error handling guidance, no recovery paths, no validation rules stated in descriptions. Naming is clear (verb_noun pattern), but parameter documentation falls short of production standards.
Takes raw commit history from get_commits() tool and formats it into a descriptive, professional standup message (e.g. 'Yesterday I fixed bug X, added feature Y')
Reads current repo's git commit history with date filters
Parameter descriptions missing or incomplete. In get_commits, time_period enum has null description. In generate_standup_message, hash, message, and author fields lack descriptions entirely. LLMs cannot infer parameter meaning from names alone.
Output schema not documented. Both tools return {content: [{type: 'text', text: string}]} but this structure is not declared in tool definitions. LLMs cannot plan downstream calls or extract structured data without knowing response shape.
No error handling or recovery guidance. If git command fails (invalid repo_path, permission denied, git not installed), tool returns raw execSync error. LLM receives stack trace with no actionable next step.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Parameter constraints not stated in descriptions. max_commits has no min/max bounds (unbounded integers invite absurd values). time_period enum values are present but not explained (what does 'this_week' mean exactly? Monday-Sunday? ISO week?).
Tool descriptions lack context for selection. get_commits says 'Reads current repo's git commit history with date filters' but does not explain when to use it vs other tools, what format commits are returned in, or whether it requires authentication.