A notes management system with MCP (Model Context Protocol) support for AI agent integration, featuring full-text search, file management, journaling, and web-based UI
Duffel exposes 3 tools with basic descriptions and partial schemas. Tool names follow verb_noun convention (search, read, append), which is good. However, descriptions are minimal (10-50 chars), parameter descriptions are absent or trivial, and output schemas are not documented. No error handling guidance, no pagination support for search results, and no indication of which parameters are required vs optional. The tools lack the depth needed for reliable LLM invocation.
Append changelog entries to project journal
Read selected files from the notes base
Search notes with compact limits before reading full notes
Parameter descriptions missing or trivial. 'query' and 'path' lack context on format, constraints, or examples. LLMs cannot infer whether 'path' is a file path, URI, or database key.
Tool descriptions are under 50 characters and lack WHEN/WHY context. 'Search notes with compact limits before reading full notes' hints at a workflow but does not explain when to call search vs read, or what 'compact limits' means.
No output schema documented. LLMs cannot plan downstream calls or extract required fields (e.g., does search return file paths, IDs, or content?). Breaks tool chaining.
duffel_search lacks pagination (limit parameter exists but no offset/cursor, no total count). Returning all results risks context window exhaustion; capping at 20-50 and offering pagination is standard.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 45 | 2026-07-28+ | v2 |
No error handling guidance. If a file is not found or append fails, the LLM receives no recovery hint (e.g., 'Try search_notes() first' or 'Check path format'). Agents cannot self-correct.