Loading ToolBench
An MCP server for managing sticky notes with Gmail email notifications
Three tools with basic schemas and descriptions, but significant gaps in parameter documentation and error handling. add_note and delete_note have minimal descriptions (under 100 chars). No parameter descriptions for add_note's 'message' field. delete_note lacks error recovery guidance. read_notes is well-structured but minimal. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Output schemas are implicit (return strings) rather than formally documented. Error messages in delete_note are helpful but inconsistent across tools.
Adds a new note to the notes file.
Delete a specific note by its index (1-based).
Read and return all notes from the sticky note file.
Parameter 'message' in add_note lacks description. LLMs cannot infer whether to pass raw text, formatted markdown, or structured data.
No tool annotations (destructiveHint, readOnlyHint, idempotentHint). Agents cannot determine which tools are safe to retry or have irreversible side effects.
Output schemas not formally documented. Descriptions state return type as string but do not specify structure, field names, or format (e.g., newline-separated notes vs JSON array).
delete_note error handling is good (invalid index message includes valid range), but add_note and read_notes lack error recovery guidance. No guidance on what to do if file is corrupted or inaccessible.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 48 | 2026-07-28+ | v2 |
add_note sends email notifications as a side effect but does not document this behavior in the description. Agents cannot predict this external action.