An MCP server for managing sticky notes with add, read, and remove operations
Three tools with basic verb-noun naming (add_note, read_notes, remove_notes) and docstring descriptions present. However, descriptions are minimal (10-30 chars), parameter descriptions are absent, input schemas lack type information beyond string, and output schemas are undocumented. No error handling guidance, no pagination support, and destructive operations (remove_notes) lack confirmation patterns. Tool composition is reasonable but lacks idempotency guarantees and recovery guidance.
Append a new note to the sticky note file.
Read and return all notes from the sticky note file.
Remove all the notes from the sticky note file.
Destructive operation (remove_notes) lacks confirmation or dry-run pattern. No guard against accidental data loss.
Tool descriptions are under 20 characters and lack WHAT/WHEN/WHY context. LLMs cannot determine when to select these tools over alternatives.
Input schemas present but lack parameter descriptions. 'message' parameter in add_note has no guidance on format, length, or constraints.
Output schemas are undocumented. LLMs do not know what fields to expect from tool responses, blocking downstream composition.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 39 | 2026-07-28+ | v2 |
No error handling guidance. Tools return plain strings ('Note saved!', 'Notes removed!') without actionable recovery hints for failure cases.