MCP server for integrating with Redmine project management system to manage issues and log time entries
Two tools with basic schemas but significant quality gaps. Tool names lack clarity (get-latest-issue vs log-time naming inconsistency). Descriptions are minimal (10-50 chars, below 194-char baseline). Parameter descriptions exist but lack constraints, ranges, and format guidance. No output schema documentation. Error handling returns plain text without recovery guidance. Missing idempotency hints for write operations. Code contains debug logging ('VISHAL TESTING') indicating incomplete development.
Get the most recent issue assigned to me
Log time to the most recent assigned open issue
Tool descriptions are too short (10-50 chars vs 194-char baseline). 'Get the most recent issue assigned to me' and 'Log time to the most recent assigned open issue' lack context for LLM selection, WHEN to use them, and prerequisites.
Parameter descriptions lack constraints and format guidance. 'spent_on' says 'Date of work (YYYY-MM-DD)' but no validation that input matches format. 'hours' lacks min/max bounds (should be 0.01 - 24 or similar). LLMs will pass invalid values.
No output schema documented. Callers cannot predict response structure. get-latest-issue returns text with ID/Subject/Project/UpdatedOn but no formal schema. log-time returns success message but no structured confirmation (issue_id, time_entry_id, etc.).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 38 | 2026-07-28+ | v2 |
Error handling returns plain text without recovery guidance. 'Failed to fetch latest issue: 404 Not Found' tells LLM nothing actionable. Should say 'No issues assigned to you. Try searching for unassigned issues or check project permissions.'
log-time is non-idempotent (creates time entries) but lacks confirmation/dry-run pattern. Agents retrying on transient failures will double-log hours. No idempotentHint annotation.