A sticky notes management server with add, read, and summarize capabilities
This server has 2 tools with basic functionality but significant quality gaps. Both tools have descriptions that are present but lack precision and fail to meet LLM-optimization baselines. Naming is reasonable (verb_noun pattern) but descriptions are generic. Input schemas are minimally structured, add_note has a basic string parameter but read_notes has an empty input object. Output schemas are completely undocumented, violating the critical baseline that '100% of A+ tools have documented return types.' Error handling is absent: tools do not guide recovery or categorize failures (pattern:recovery-guide). No parameter validation or actionable error messages. The server includes a resource (notes://latest) and prompt (note_summary_prompt) which add some feature completeness, but core tool quality is weak. Average tool score: 38/100.
Append a new note to the sticky file in bullent points. Args: message (str): The content of the sticky note to be added. Returns: str: Confirmation message indicating the note has been added.
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.
Output schemas completely undocumented. Both tools return strings but return type structure and fields are not declared. LLMs cannot plan downstream tool calls or extract structured data from responses.
Descriptions are generic and under 50 characters, well below the 194-char baseline for production tools. 'Append a new note to the sticky file in bullent points' (typo: 'bullent') does not explain when to use this tool, any prerequisites, or distinguish it from similar operations. LLMs cannot reliably select the right tool with such sparse guidance.
No error handling or recovery guidance. Tools do not validate input (e.g., null/empty message in add_note) or return actionable error messages. If file I/O fails, the LLM receives nothing indicating what to do next.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 41 | 2026-07-28+ | v2 |
read_notes has empty input schema ({}). While technically correct for a no-argument tool, the JSON Schema is not explicitly typed or validated. Input parameter documentation is absent.
No destructive operation warnings or confirmation pattern. add_note modifies persistent state but is not marked with any hints (e.g., idempotentHint, destructiveHint) to inform the agent of side effects.
No pagination or result limits declared. read_notes returns all notes as a single concatenated string. If notes file grows large, response token count could explode. No limit stated in description; no pagination API offered.