Loading ToolBench
MCP server that synchronizes documentation with codebase changes by detecting documentation drift and applying updates based on git diffs
Single tool 'execute_skill_action' has critical definition gaps. Input schema is present but severely underdeveloped: 'git_diff_summary' and 'doc_structure' lack type constraints, validation rules, and detailed descriptions. The tool description (67 chars) is below the 194-char baseline and lacks WHEN/WHY guidance. No output schema is documented, the response structure is inferred from client.py mock data, not formally specified. No error handling, recovery guidance, or parameter constraints. The tool combines multiple concerns (detect drift + apply updates + generate diagrams) violating single-responsibility. No tool annotations (destructiveHint, idempotentHint). This server would not pass code review.
Execute documentation synchronization action to detect and apply codebase-driven documentation updates
Input schema lacks type constraints and validation rules. 'git_diff_summary' is a bare string with no format/length limits; 'doc_structure' is an untyped object. No enum constraints, regex patterns, or range limits.
No output schema documented. Response structure (docs_updated_count, updated_documents, documentation_drift_score, etc.) is inferred from mock client code, not formally specified in tool definition. LLM cannot plan downstream operations.
Tool description is 67 characters (below 194-char baseline). Lacks WHAT/WHEN/WHY guidance. Does not explain when to call this vs other documentation tools, what prerequisites exist, or what side effects occur.
Tool combines multiple responsibilities: detect documentation drift, apply updates, and generate diagrams. Should split into separate tools (detect_doc_drift, apply_doc_updates, generate_diagrams) for composability.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
No error handling or recovery guidance. No indication of retryable vs fatal errors, no actionable error messages, no guidance on what to do if documentation drift is detected but updates fail.