Manage your TickTick tasks, projects, habits, focus sessions, tags, countdowns, and statistics through natural language.
The server defines 4 countdown tools with clear verb-noun naming (list_, create_, update_, delete_). All tools have descriptions and input schemas with typed parameters. However, descriptions are minimal (10-50 chars), lack context on when to use each tool, and omit dependency hints. Parameter descriptions are present but terse. Output schemas are not documented. Error handling exists but is generic. The server demonstrates basic competence but falls short of production-grade quality expected for A/B grades.
Create a new countdown timer.
Delete a countdown.
List all countdowns. Returns countdown id, name, date, type, and color.
Update an existing countdown.
Tool descriptions are too brief (10-50 chars) and lack context. 'Create a new countdown timer' does not explain when to use this vs update_countdown, what fields are required vs optional, or what the response contains. LLMs cannot reliably select the right tool without richer guidance.
Output schemas are not documented. The tools return JSON objects but the response structure (fields, types, example values) is not visible in the tool definitions. LLMs cannot plan downstream operations or extract the right data without knowing what fields to expect.
Parameter descriptions are minimal and lack format/constraint guidance. For example, 'date' parameter says 'Target date in "YYYY-MM-DD" format' but does not clarify if past dates are allowed, whether the date must be in the future, or what happens if the date is invalid. 'color' parameter has no description of valid values (hex codes? named colors? range?).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
No error handling guidance. The error-handler.ts maps errors to text responses but does not categorize them as retryable, user-fixable, or fatal. An LLM receiving 'API error (400): Invalid countdown ID' has no guidance on whether to retry, ask the user, or abort.
delete_countdown lacks a confirmation or dry-run pattern. Destructive operations should support a confirmation step to prevent accidental deletion. The tool is marked DESTRUCTIVE but offers no safeguard.