Loading ToolBench
Read and write Memlog notes over HTTP. Tools: list_notes, search_notes, get_note, create_note, append_to_note, update_note, delete_note, list_tags.
Memlog MCP has well-structured tool definitions with consistent naming (verb_noun pattern), clear descriptions (avg 85 chars), and complete input schemas with types and descriptions. All 8 tools follow the verb-first convention (list_, search_, get_, create_, append_, update_, delete_). Descriptions are concise and action-oriented. However, output schemas are not documented, LLMs cannot predict response structure for planning downstream calls. Parameter descriptions are present but lack format constraints (e.g., sort field enums, limit ranges). No error handling guidance or recovery paths documented. Destructive operations (delete_note) lack confirmation patterns. Missing tool annotations (readOnlyHint, destructiveHint) despite clear risk classifications in metadata.
Append content to the end of an existing note. Safer than update_note — existing content is never overwritten.
Create a new note.
Delete a note permanently.
Get the full content of a note by title.
List all notes with title and lastModified timestamp (no content).
Return all tags currently used across notes.
Search notes by keyword, phrase, or #tag. Use * for all notes.
Output schemas not documented. LLMs cannot predict response structure (fields, types, pagination) for planning multi-step workflows. E.g., list_notes and search_notes should document returned fields (title, lastModified, content_preview, tag_list) and pagination info.
Parameter constraints missing. sort field in list_notes and search_notes lacks enum (e.g., 'title', 'lastModified', 'created'). limit parameter lacks range (should be 1-100 or similar). order lacks enum ('asc'|'desc'). LLMs will hallucinate invalid values.
No error handling guidance. Tools lack recovery hints. E.g., get_note should document 'Note not found, try search_notes() to find the correct title.' delete_note should warn 'This is permanent and cannot be undone.'
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 66 | 2026-07-28+ | v2 |
Update an existing note's content or title.
Destructive operations lack confirmation pattern. delete_note should support dry-run or require explicit confirmation before permanent deletion. Agents make mistakes, no safeguard prevents accidental data loss.
Tool annotations missing. FastMCP supports readOnlyHint, destructiveHint, idempotentHint but none are declared. Metadata shows risk classifications (READ_ONLY, WRITE, DESTRUCTIVE) but not exposed to MCP protocol. LLMs cannot infer safety properties.