Summary
memory_store does not validate that content is present and non-empty before persisting a memory. Calling the tool with an empty body or blank content succeeds and creates a useless memory record.
Steps to Reproduce
- Call
memory_store with an empty argument object:
- Alternatively, call with an empty string:
Expected Behavior
The API should reject the request with a clear validation error, e.g.:
Validation should happen before embedding is invoked.
Actual Behavior
The request succeeds and stores an empty memory, e.g.:
Stored memory 019efebd2e9d7ec39a3e95b910e1daab:
Impact
- Pollutes the memory store with empty records
- Wastes embedding API calls
- Makes downstream retrieval noisier
Environment
- MCP server:
http://localhost/memoria-api/mcp
- Tool:
memory_store
- Discovered during functional testing on 2026-06-25
Suggested Fix
Add server-side validation to reject missing or whitespace-only content before embedding/persistence.
Summary
memory_storedoes not validate thatcontentis present and non-empty before persisting a memory. Calling the tool with an empty body or blank content succeeds and creates a useless memory record.Steps to Reproduce
memory_storewith an empty argument object:{}{ "content": "" }Expected Behavior
The API should reject the request with a clear validation error, e.g.:
Validation should happen before embedding is invoked.
Actual Behavior
The request succeeds and stores an empty memory, e.g.:
Impact
Environment
http://localhost/memoria-api/mcpmemory_storeSuggested Fix
Add server-side validation to reject missing or whitespace-only
contentbefore embedding/persistence.