FastMCP server for managing Telegram reminders with CRUD operations. Provides tools to create, list, edit, delete reminders and track due reminders for Telegram users.
Server has 6 tools with complete input schemas and basic descriptions. Naming follows verb_noun convention (create_, list_, edit_, delete_, get_, mark_). However, descriptions are minimal (10-50 chars), lacking context on WHEN to use each tool and what happens on error. Parameter descriptions are present but terse. Output schemas are not documented, LLMs cannot predict response structure. Error handling returns JSON but lacks recovery guidance. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels. Overall: functional but below production baseline (194 char avg description; 100% of A+ tools have rich docstrings).
Create a new reminder.
Delete a reminder.
Edit an existing reminder.
Get all reminders that are due and haven't been sent yet.
List all active (unsent) reminders for a specific user.
Mark a reminder as sent.
Descriptions are 10 - 50 characters; rubric baseline is 194 chars. Lack context on WHEN to use each tool, prerequisites, and side effects. E.g., 'Create a new reminder' does not explain that due_time must be future-dated or what happens if it's in the past.
Output schemas are not documented. Tools return JSON strings but LLMs cannot predict field names, types, or structure. E.g., create_reminder returns {status, message, reminder} but this is not declared in the tool definition.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). delete_reminder and edit_reminder are destructive but not marked. list_reminders and get_due_reminders are read-only but not marked. LLMs cannot infer safety/retry semantics.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Error messages lack recovery guidance. E.g., 'Unauthorized: This reminder does not belong to you' does not suggest next steps. Rubric requires: 'User not found. Try search_users() with a partial name.' Pattern: recovery-guide.
Parameter descriptions are terse (5 - 20 chars). E.g., 'The Telegram chat ID of the user' is present but does not explain format (integer, positive), range, or how to obtain it. Rubric: 'The project key (2-10 uppercase letters, e.g. PROJ)' is actionable.