MCP server for Jira-based workflow analytics, forecasting, and flow metrics (Monte Carlo simulations, cycle time analysis, WIP stability, aging analysis, CFD, throughput, yield, flow debt)
Scoring was not performed
Output schemas completely undocumented. No tool declares return type structure, field names, or types. LLMs cannot chain tools or extract data without guessing at response format.
Parameter constraints missing. 'bucketType', 'buckets', 'mode', 'percentile' lack enum definitions, min/max bounds, or format specifications. LLMs cannot infer valid values.
Descriptions lack actionable LLM guidance. Descriptions are domain-specific (e.g., 'Understand baseline SLE') but do not explain WHEN to call the tool, WHAT to expect, or HOW to use results. Baseline is 194 chars; observed avg ~130 chars.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 30 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 49 | - | v1 |
No error handling or recovery guidance visible in tool definitions. Tools return generic errors with no actionable next steps for LLMs.
forecast_monte_carlo has 15 parameters with minimal descriptions. Highly complex tool without guidance on parameter relationships or valid combinations.
Inconsistent naming pattern. 'import_*' tools use different verb than analytical 'analyze_*' and 'forecast_*' tools. Cognitive load when selecting among 23 similar tools.