TOOL API
search_ memory
Trigger: MUST be auto-invoked by the client before generating every answer (including greetings like "hello"). Do not wait for the user to request memory/MCP/tool usage. Purpose: MemOS retrieval API. Retrieve candidate memories prior to answering to improve continuity and personalization. Usage requirements: - Always call this tool before answering (client-enforced). - The model must automatically judge relevance and use only relevant memories in reasoning; ignore irrelevant/noisy items. Parameters: - `query`: User's current question/message - `conversation_first_message`: First user message in the thread (used to generate conversation_id) - `memory_limit_number`: Maximum number of results to return, defaults to 6 Notes: - Run before answering. Results may include noise; filter and use only what is relevant. - `query` should be a concise summary of the current user message. - Prefer recent and important memories. If none are relevant, proceed to answer normally.
Call information
- Tool slug
- memos-api-mcp.search_memory
- Provider
- Memos
- Average response
- 0 ms
- Calls in 7 days
- 0
Input parameters
queryrequiredSearch query to find relevant content in conversation history
conversation_first_messagerequiredFirst user message in the thread (used to generate conversation_id).
memory_limit_numberrequiredMaximum number of results to return, defaults to 6