An MCP server for managing sticky notes with file-based persistence
Three tools with basic descriptions and minimal parameter documentation. add_note has a single string parameter with description; read_notes and get_note_filename have no parameters. Descriptions are present but brief (10-40 chars for some). No input schemas visible in source, FastMCP decorators infer schemas from type hints, but explicit schema definitions are not shown. No output schemas documented. No error handling guidance, no recovery paths, no validation rules. Tools lack idempotency hints and destructive operation warnings. Composition is reasonable (three separate concerns), but parameter descriptions are sparse and output structure is undocumented.
Append a new note to the sticky note file.
Return the filename used for storing notes.
Read and return all notes from the sticky note file.
No explicit input/output schemas visible. FastMCP infers from type hints, but schemas are not documented in source. Cannot verify parameter constraints, enums, or output field structure.
add_note is destructive (writes to file) but has no confirmation step, dry-run option, or idempotency hint. Agents may retry and create duplicate notes.
No error handling guidance. If file operations fail (permissions, disk full), tools return raw exceptions. LLM has no recovery path.
get_note_filename returns an absolute file path. This is a security/privacy leak, exposes internal directory structure to the LLM and user. Should return only the filename or a resource URI.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
Parameter descriptions are minimal or absent. 'message' in add_note has a description, but no constraints on length, format, or content type are documented.