Loading ToolBench
MCP server for triaging and assigning engineering issues to Linear agile cycles based on user feedback
Single tool 'execute_skill_action' has a basic description but critical gaps in schema completeness, parameter documentation, and output specification. Input schema is visible but parameters lack individual descriptions. No output schema documented. Tool name uses 'and' pattern (execute + skill + action) suggesting multiple responsibilities. No error handling guidance, no idempotency markers, no security considerations. Descriptions are present but minimal (under 100 chars). This server falls well below production baseline.
Execute the Linear Agile Cycle Issue Triage skill to triage and assign engineering cycles
Tool name 'execute_skill_action' violates single-responsibility principle, combines 'execute', 'skill', and 'action' suggesting multiple concerns. Should be 'triage_issue' or 'assign_engineering_cycle'.
Input parameters 'raw_user_feedback' and 'current_active_cycle' lack individual descriptions in schema. LLMs cannot infer parameter meaning from names alone, 'raw_user_feedback' could be structured or unstructured; 'current_active_cycle' format is undefined.
No output schema documented. Tool returns 7 fields (triage_issue_id, issue_title, priority_level, cycle_assigned, estimated_story_points, suggested_assignee_domain, git_branch_slug, linear_sync_ready) but LLM has no formal specification of types, constraints, or field meanings.
No error handling guidance. Tool description does not explain failure modes, recovery steps, or when to retry. LLM cannot distinguish retryable errors from user-fixable ones.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 36 | 2026-07-28+ | v2 |
Tool description (95 chars) is minimal and lacks context on WHEN to use it, WHAT it returns, or HOW it differs from related tools. Does not state that this modifies state (creates issues, assigns cycles).