MCP server for GitHub issue prioritization and workflow management
Critical gaps across all dimensions. Tool definitions lack input schemas (cannot verify parameter types/constraints), descriptions are minimal or missing, and no output schemas are documented. 15 tools registered but source code inspection reveals incomplete definitions. No tool annotations (readOnlyHint/destructiveHint). Error handling is absent, no recovery guidance or actionable error messages. Naming is verb-based (positive), but parameter documentation is sparse. This server would require substantial rework before production use.
No input schemas visible in source code. Cannot verify parameter types, constraints, or descriptions. All 15 tools score 0 on schema dimension.
Tool descriptions are minimal (15 chars or less). LLMs cannot determine when/why to select tools. Descriptions must be 50-200 chars explaining WHAT, WHEN, and WHAT IT RETURNS.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 33 | <=2025-11-25 | v2 |
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). LLMs cannot distinguish safe reads from destructive writes. 8 WRITE tools lack destructiveHint; 7 READ_ONLY tools lack readOnlyHint.
No error handling or recovery guidance visible. Tools do not return actionable error messages. LLMs cannot self-correct or know whether to retry.
No output schemas documented. LLMs cannot plan downstream tool calls or extract required fields (e.g., issue_id from create_issue for chaining to claim_issue).