Self-evolving MCP memory & belief engine: SQLite WAL + Causal Memories + ChromaDB semantic + file docs
Two tools with minimal descriptions and incomplete schemas. 'recall' has a reasonable 89-char description and three typed parameters (query, limit, min_score), but lacks output schema documentation. 'memory_context' has only a 95-char description and zero input parameters, making it difficult for LLMs to understand when to invoke it or what it returns. Neither tool has error handling guidance, recovery hints, or composition context. Parameter descriptions are present but generic. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite both being READ_ONLY. Output schemas are completely undocumented, LLMs cannot plan downstream calls or extract structured data.
Compact metadata snapshot for context scenting across all memory layers
Unified search across all 3 layers (facts, semantic, documents) in one call
Output schemas completely undocumented. 'recall' returns search results but LLMs cannot infer field names, types, or structure. 'memory_context' returns a 'metadata snapshot' with no schema definition.
No tool annotations despite both tools being READ_ONLY. Missing readOnlyHint metadata prevents LLMs from understanding safety properties and retry semantics.
'memory_context' has zero input parameters but description says 'Compact metadata snapshot for context scenting across all memory layers', unclear what triggers it or what it returns. No output schema.
No error handling guidance. If 'recall' finds zero results, returns invalid JSON, or hits a timeout, LLMs have no recovery path. No actionable error messages documented.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |
Parameter descriptions are minimal. 'min_score' lacks context on valid range (0 - 1? 0 - 100?), what score means, or when to use it. LLMs will guess.