recall · diff
git:20260709.f4c06a1 to git:20260713.d4415d7
8 added, 13 removed. Audit A to A.
---
name: recall
- description: Inject relevant memories as structured context for the current task. Use when starting complex work that may benefit from past decisions or notes.
- argument-hint: [topic or question]
- allowed-tools: mcp__plugin_memtomem_memtomem__mem_search, mcp__memtomem__mem_search, mcp__plugin_memtomem_memtomem__mem_do, mcp__memtomem__mem_do
+ description: Recall memtomem memories created in a date range. Use for recent memories or requests scoped by day, week, month, source, or namespace.
+ argument-hint: [date range]
+ allowed-tools: mcp__plugin_memtomem_memtomem__mem_recall, mcp__memtomem__mem_recall
---
- Search for relevant memories about: $ARGUMENTS
+ # Recall memories
- ## Instructions
+ Use `$ARGUMENTS` as the date range or recent-memory request.
+ If the request does not clearly specify the date range or recent-memory request, ask before calling a tool.
+ Translate relative dates such as “last week” into `since` and `until` values when possible, then call `mem_recall`. Preserve any source, namespace, scope, or result-limit constraint from the request.
- 1. Use `mem_search` with the topic as query (top_k=5)
- 2. For each high-relevance result (score > 0.5), call `mem_do` with `action="related"` and `params={"chunk_id": <result's chunk_id>}` to find linked memories (`mem_related` is non-core; `mem_do` routes to it in the default `core` tool mode)
- 3. Present results grouped by namespace, showing:
- - Source file and heading
- - Tags for quick categorization
- - Full content for top 3, summary for the rest
- 4. If cross-references exist, show the relationship chain
- 5. Suggest which memories are most relevant to the current task
+ Present memories newest first with their creation date and source. Ask for a date range only when the request provides no usable temporal constraint. Use topic search, not recall, when the user is asking what a memory says rather than when it was created.