Shared memory runtime for AI agents. One local .wax store shared by your whole agent team over MCP. Provides durable on-device memory tools (remember, recall, search, forget) for Foundation Models and MCP clients.
Wax MCP Server has significant quality gaps across definition dimensions. Only 5 of 34 tools (15%) have detailed input schemas with type information and descriptions. The remaining 29 tools (85%) appear to be inferred from a 'broker command catalog' with minimal or no visible parameter definitions. Tool names lack consistency, some use verb_noun pattern (waxMemory, waxRemember, waxRecall, waxForget) while others are nouns only (remember, recall, search, stats, handoff). Descriptions vary wildly: 5 tools have comprehensive docstrings (100-350 chars) explaining use cases and prerequisites, while 29 have only 2-7 word phrases like 'Store durable memory' or 'Check memory health' that provide minimal LLM guidance. No explicit output schemas are documented in the visible code. Critical pattern violations include: (1) 85% of tools lack parameter-level documentation, violating pattern:tool-description; (2) no error handling documentation or recovery guides; (3) no indication of idempotency, permission requirements, or destructive operation guards; (4) composition breaks: multiple tools (waxMemory, remember, memory_append, memory_promote, promote) do similar memory operations with unclear distinctions, violating pattern:tool composability. Tools 7-34 appear entirely inferred from test/schema files without explicit handler implementations visible.
Compact context (broker command catalog)
Search corpus (broker command catalog)
Resolve entity (broker command catalog)
Upsert entity (broker command catalog)
Assert fact (broker command catalog)
Retract fact (broker command catalog)
Query facts (broker command catalog)
85% of tools (29 of 34) lack visible input parameter schemas. Parameter types, descriptions, constraints, and validation rules are not documented or visible in source.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 46 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 0 | - | v1 |
Handoff (broker command catalog)
Handoff latest (broker command catalog)
Capture knowledge (broker command catalog)
Export as markdown (broker command catalog)
Sync markdown (broker command catalog)
Append to memory (broker command catalog)
Get memory (broker command catalog)
Check memory health (broker command catalog)
Promote memory (broker command catalog)
Search memory (broker command catalog)
Promote (broker command catalog)
Recall memory (broker command catalog)
Store durable memory (remember action via broker command catalog)
Search memory (broker command catalog)
Close a session (broker command catalog)
End a session (broker command catalog)
Open a session (broker command catalog)
Resume a session (broker command catalog)
Start a session (broker command catalog)
Synthesize session memory (broker command catalog)
Get statistics (broker command catalog)
Migrate task state (broker command catalog)
Forget durable Wax memory matching a query by deleting up to topK frames. Use when the user asks to forget, delete, remove, or erase prior stored facts.
Manage persistent on-device memory in Wax. - action=remember (aliases: store, save): store durable facts, preferences, decisions. - action=recall (aliases: get, lookup): retrieve the best context for a query. - action=search (aliases: find, query): ranked memory hits with optional topK and hybrid alpha. - action=forget (aliases: delete, remove, erase): delete matching memory frames for a query. Do not store secrets or one-off ephemeral chatter.
Recall the most relevant durable memories for a natural-language query. Use before answering questions about user preferences, past decisions, or prior context.
Store a durable fact, preference, or decision in on-device Wax memory. Use for information that should survive across sessions. Do not store secrets.
Search durable Wax memory and return ranked hits. Use when you need broader retrieval or want to control result count via topK.
29 tools have descriptions under 25 characters ('broker command catalog' descriptors).
Multiple tools (waxMemory + remember + memory_append + memory_promote; waxRecall + recall + memory_search + memory_get; waxForget + search) perform similar or overlapping memory operations with no clear semantic distinction. LLMs will struggle to choose between them. Violates pattern:tool composability (each tool should do exactly one thing, and multiple tools operating on the same resource must have obvious distinctions).
No output schemas documented. Tools do not specify what fields they return, making it impossible for LLMs to plan downstream calls or extract necessary data for chaining. Violates pattern:tool (document output schema) and mxe:include-chaining-ids (responses must return IDs for downstream tool use).
No error handling documentation. No tools include guidance on what errors are retryable, user-fixable, or fatal. No recovery paths or actionable error messages. Violates pattern:recovery-guide and pattern:error-classification.
Destructive tools (waxForget, fact_retract, etc.) lack confirmation or dry-run support. No indication of idempotency. Violates pattern:confirmation-request.
Tool names lack consistency. 5 tools follow verb+noun (waxRemember, waxRecall, waxSearch, waxForget) but also have noun-only aliases (remember, recall, search). 29 tools use inconsistent patterns: some noun-only (stats, handoff, promote), some verb+noun (session_start, entity_upsert), some descriptive (compact_context, markdown_export). LLMs cannot reliably infer intent from such inconsistency.