Loading ToolBench
MCP server for team-management: issue tracking, git/MR, code review, DAIC mode, protocol engine, notifications, release, and config tools. Exposes 42 MCP tools across 8 tool modules with automatic provider detection and routing.
39 tools with inconsistent quality. Most have basic descriptions (50-150 chars) and input schemas present, but lack depth. Parameter descriptions are minimal (10-30 chars). No output schemas documented. Error handling absent, tools return raw API responses without recovery guidance. Naming is verb-noun compliant but many tools are overly granular (issue_sync, issue_push, issue_link, issue_unlink are near-duplicates). No tool annotations (readOnlyHint/destructiveHint). Security concerns: issue_api exposes raw HTTP method/endpoint/data parameters, inviting injection attacks. DAIC mode and protocol tools lack clear state management documentation. Composition issues: 12 issue-tracking tools could consolidate into 4-5 with better parameter design.
Perform code review on specified files or changes
Get configuration values
Update configuration values
Disable DAIC mode
Enable DAIC (Discussion-Alignment-Implementation) mode
Get the current DAIC mode status
Fetch code review for a merge request
Create a git commit with specified changes
Push commits to remote repository
issue_api tool exposes raw HTTP method/endpoint/data parameters without validation or sanitization, creating SQL injection, command injection, and path traversal attack surface. LLMs can be tricked into passing malicious payloads.
No output schemas documented for any of 39 tools. LLMs cannot plan downstream calls or extract required fields (e.g., issue_id from issue_create). Responses likely include verbose API metadata, wasting tokens and increasing hallucination risk.
12 issue-tracking tools (issue_sync, issue_push, issue_link, issue_unlink, issue_dependency, issue_comment, issue_set_status, issue_update, issue_create, issue_read, issue_status, issue_api) are overly granular and partially redundant. issue_sync and issue_push have identical descriptions. Consolidate into 4-5 composable tools with richer parameters.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
Make a direct API call to the issue tracking provider
Add a comment to an issue
Create a new issue in the configured issue tracking provider
Manage dependencies between issues (Gitea full support, GitHub same-repo only)
Link an issue to another issue or resource
Push local issue changes to the configured issue tracking provider
Read the full details of an issue from the configured issue tracking provider
Set the status of an issue
Get the status of an issue from the configured issue tracking provider
Synchronize issue state with the configured issue tracking provider
Remove a link between issues or resources
Update an existing issue in the configured issue tracking provider
Add a comment to a merge request
Create a merge request
Update an existing merge request
Discover available Telegram chats for notifications
Get the status of notifications
Send a notification to the user
Get configuration for a protocol
End the current protocol execution
List available protocols
Pause a protocol execution
Reset a protocol to its initial state
Resume a paused protocol execution
Start a protocol execution
Get the current status of a protocol
Advance to the next step in a protocol
Validate a protocol configuration
Add a comment to a pull request
Create a new release
No error handling guidance. Tools return raw API responses without recovery hints. E.g., 'Issue not found' should suggest 'Try issue_status() with a different issue_id' or list available issues. Agents cannot self-correct.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes. issue_sync and issue_push lack clarity on idempotency, agents may retry and cause duplicate side effects.