A sticky notes MCP server that allows adding, reading, and managing notes with prompt generation capabilities
Two tools with basic descriptions and minimal parameter documentation. add_note has a single string parameter with description; read_notes has no parameters. Both descriptions are present but generic (under 200 chars). No input validation, error handling guidance, or output schema documentation. No tool annotations (readOnlyHint, destructiveHint). Naming is verb-based (add_, read_) which is correct, but descriptions lack context on when to use each tool or what happens on failure. No pagination, no structured output schema, no recovery guidance for errors.
Append a new note to the sticky note file. Args: message (str) : The note content to be added. returns: str: Confirmation message indicating the note was saved.
Read and return all notes from the sticky note file. Returns: str: All notes as a single string separated by line breaks. If no notes exist, a default message is returned.
No output schema documentation. Tools return plain strings; LLMs cannot infer structure or plan downstream calls.
No error handling or recovery guidance. If file I/O fails or notes.txt is corrupted, tools return nothing actionable.
Missing tool annotations. add_note is destructive (WRITE) but lacks destructiveHint; read_notes is read-only but lacks readOnlyHint.
Descriptions lack context on when to use each tool or what happens on error. 'Append a new note' and 'Read and return all notes' are functional but do not guide LLM selection.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
No input validation or constraint documentation. add_note accepts any string; no length limits, encoding constraints, or format guidance.