Per-agent semantic memory over SQLite + local embeddings (pure-Rust tract backend). MCP server for storing, recalling, and consolidating agent memories with vector embeddings.
Genesis Memory Server has 3 tools with basic schemas and descriptions, but significant gaps prevent production use. Tool names are action-oriented (store, recall, consolidate), but descriptions lack depth on when/why to use each tool and what they return. Input schemas are present but incomplete: parameters lack type constraints (enums for 'type' field), and output schemas are entirely undocumented. No error handling guidance, no pagination support for recall results, and no idempotency guarantees despite write operations. The 'consolidate' tool's optional 'source_db' parameter invites path traversal attacks without validation hints.
Consolidate and deduplicate memories from multiple sources into the canonical database
Retrieve semantically similar memories from the vector database
Store a memory record in the vector database with semantic embeddings
Output schemas completely undocumented. No specification of what store/recall/consolidate return, forcing LLMs to guess field names and types. Breaks tool chaining and context planning.
Descriptions too brief (30-40 chars) and lack actionable context. 'Store a memory record' does not explain when to call store vs consolidate, what happens on duplicate text, or whether the call is idempotent. Baseline: 194 chars average.
'type' parameter in store tool has no enum constraint or validation hint. LLMs will hallucinate arbitrary type values instead of selecting from a known set (e.g., 'fact', 'event', 'relationship').
recall tool accepts 'limit' parameter but no pagination guidance. Returning 10+ memories as unstructured text wastes tokens and risks context window exhaustion. No next_cursor or total_count documented.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 46 | <=2025-11-25 | v2 |
consolidate tool's 'source_db' parameter (file path) lacks validation hints or security guidance. No mention of path traversal prevention, allowed directories, or format constraints. Invites injection attacks.