Loading ToolBench
MCP server for issue and project management with artifact lifecycle support
IssueBoss demonstrates solid tool design with 17 well-named, verb-prefixed tools covering issue lifecycle, artifacts, and relationships. All tools have descriptions (avg 120 chars) and input schemas with typed parameters. However, output schemas are not documented in the provided source, parameter descriptions lack constraint details (enums, ranges, formats), and error handling guidance is absent. Tool composition is strong, each tool has a single responsibility and names clearly distinguish operations (list_issues vs list_open_issues). Parameter naming is consistent (issue_slug, artifact_slug). Missing: enum constraints for status/priority/size values, documented output structures, and recovery guidance in error scenarios.
Add an artifact (TriageResult, Spec, Research, Plan, ResearchTopic, Comment, Handoff) to an issue with JSON body.
Add a relationship between two issues (DependsOn or RelatedTo).
Create a new issue in a project with title, optional description, priority, and size.
Get full details of a specific artifact by issue slug and artifact slug.
Get full details of a specific issue by slug.
Get details of a specific project by slug.
List artifacts for an issue with optional filtering by kind and uncovered research topics.
Output schemas not documented. Tools return structured data but LLMs cannot see field names, types, or required fields. Downstream tool chaining requires guessing response structure.
Enum constraints missing for status, priority, size, and artifact kind parameters. Descriptions say 'e.g. High' but do not declare valid values formally. LLMs may hallucinate invalid values.
Error handling guidance absent. Tools declare error risk (WRITE, DESTRUCTIVE) but provide no recovery hints. LLMs cannot determine if errors are retryable or require user intervention.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 63 | <=2025-11-25 | v2 |
List issues in a project with optional filtering by status, priority, size, submitter, and assignee. Can return compact summary rows or full issue objects.
List open issues in a project with optional filtering by priority, size, submitter, and assignee. Returns compact summary rows by default to avoid token overflow.
List all projects accessible to the authenticated user.
List all relationships for an issue (depends_on, blocks, related_to).
Update artifact path references when files are moved on disk. All artifacts referencing old_path will be updated to new_path.
Remove an artifact from an issue.
Remove a relationship between two issues.
Transition an issue to a new status with optional reason recorded in StatusTransition artifact.
Update an existing artifact's JSON body.
Update an existing issue's title, description, priority, or size.
Parameter descriptions lack format/constraint details. 'Filter by status' does not explain valid values. 'Artifact slug' does not state 'lowercase letters, digits, hyphens only' in the description (only in add_artifact body text).
Destructive operations (remove_artifact, remove_relationship) lack confirmation or dry-run support. Agents cannot preview consequences before executing irreversible actions.