An MCP server for managing sticky notes stored in a SQLite database
Three tools with minimal descriptions (10-30 chars), no parameter descriptions, and incomplete schemas. get_notes_list has empty input schema {}; get_note and add_note use Zod validation but lack formal schema documentation. No error handling guidance, no output schema documentation, and no tool annotations. Naming is acceptable (verb_noun pattern) but descriptions are far below the 194-char baseline for production tools. This server reads like a prototype, not production-grade.
Create a sticky note
Get a sticky note by ID
Get a list of sticky notes
All three tool descriptions are under 30 characters and lack context for LLM selection. Descriptions must explain WHAT, WHEN, and any prerequisites. Baseline is 194 chars.
Parameter 'id' in get_note and 'text' in add_note have descriptions, but no output schema is documented. LLMs cannot plan downstream calls without knowing return structure.
No error handling guidance. If db_path is missing or invalid, or if a note ID does not exist, responses are silent or generic. LLMs need actionable recovery hints.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 35 | 2026-07-28+ | v2 |
add_note modifies state but description does not say so. LLMs need to know which calls are safe to retry and which have irreversible consequences.