Bill the same clients every month without remembering to. Define a recurring invoice once, then generate the real PDFs that are due into your invoice server, with month-end safe dates, an audit log and a revenue forecast. Everything stays on your machine.
mcp-recurring has 11 well-named tools with clear verb-noun patterns (schedule_create, schedule_list, invoice_generate_due, etc.). All tools have descriptions (10 - 200 chars, within baseline). Input schemas are present and typed for all tools. However, output schemas are NOT documented, the code shows tool registration but no return type documentation. Parameter descriptions are present but often terse (e.g., 'Schedule ID or client name' repeated across 6 tools). Error handling is basic; no recovery guidance or actionable error messages visible in the source. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (READ_ONLY, WRITE, DESTRUCTIVE). Composition is strong, tools chain well (schedule_list → schedule_update, invoice_generate_due → history_list). Naming is consistent and unambiguous.
List the generation history of all invoices
Generate invoices for all due periods
Skip a period for a schedule without generating an invoice
Create a new recurring invoice schedule
Delete a recurring invoice schedule
Show revenue forecast for a schedule
List all recurring invoice schedules
Pause a recurring invoice schedule
Output schemas not documented. Code shows tool registration but no return type definitions visible. LLMs cannot plan downstream calls or extract required fields (e.g., schedule_id from schedule_create response).
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite explicit risk levels in metadata (READ_ONLY, WRITE, DESTRUCTIVE). Agents cannot distinguish safe from destructive operations without parsing descriptions.
Parameter descriptions are terse and repetitive. 'Schedule ID or client name' appears in 6 tools but lacks guidance on which to prefer or how resolution works. No examples of valid formats (e.g., 'UUID or client name like "Acme Corp"').
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 69 | 2026-07-28+ | v2 |
Resume a paused recurring invoice schedule
Show upcoming invoice periods for a schedule
Update an existing recurring invoice schedule
No error handling guidance in tool descriptions. Destructive operations (schedule_delete, invoice_skip) lack confirmation or dry-run patterns. No recovery hints (e.g., 'If schedule not found, call schedule_list to verify the name').
Complex parameter 'every' accepts both string ('weekly', 'monthly') and object ({days: 10}) but description does not clarify the union type or provide examples of valid object shapes.