@prmichaelsen/remember-mcp 2.1.0 → 2.2.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1433,6 +1433,8 @@ var searchMemoryTool = {
1433
1433
  name: "remember_search_memory",
1434
1434
  description: `Search memories AND relationships using hybrid semantic and keyword search.
1435
1435
 
1436
+ **BEST FOR**: Precise searches with specific keywords or exact phrases. Good for finding specific items when you know what you're looking for.
1437
+
1436
1438
  By default, searches BOTH memories and relationships to provide comprehensive results.
1437
1439
  Relationships contain valuable context in their observations.
1438
1440
 
@@ -1447,6 +1449,15 @@ var searchMemoryTool = {
1447
1449
  - "Find memories about camping trips" \u2192 returns memories + relationships about camping
1448
1450
  - "Search for recipes I saved" \u2192 returns recipe memories + related relationships
1449
1451
  - "Show me notes from last week" \u2192 returns notes + any relationships created that week
1452
+
1453
+ **AGENT GUIDANCE**:
1454
+ - If search results are too narrow or miss relevant content, try remember_query_memory instead - it uses pure semantic search which is better for broader, concept-based queries. You can inform the user: "I didn't find what you're looking for with keyword search. Let me try a broader semantic search using the query tool."
1455
+ - **CRITICAL**: If no results are returned, DO NOT make up or fabricate memories. Only report what was actually found. Tell the user honestly that no matching memories were found and suggest they:
1456
+ * Create a new memory with the information they're looking for
1457
+ * Try the other search tool (remember_query_memory for broader semantic search)
1458
+ * Remove or relax filters if they applied any
1459
+ * Increase the limit parameter to see more results
1460
+ * Try different search terms or keywords
1450
1461
  `,
1451
1462
  inputSchema: {
1452
1463
  type: "object",
@@ -1987,6 +1998,8 @@ var queryMemoryTool = {
1987
1998
  name: "remember_query_memory",
1988
1999
  description: `Query memories using natural language for RAG (Retrieval-Augmented Generation).
1989
2000
 
2001
+ **BEST FOR**: Broad, concept-based searches and natural language questions. Uses pure semantic search to find memories by meaning, not just keywords. Great for exploratory queries and when you're not sure of exact terms.
2002
+
1990
2003
  This tool is optimized for LLM context retrieval. It returns relevant memories
1991
2004
  with their full content and context, formatted for easy consumption by LLMs.
1992
2005
 
@@ -1995,12 +2008,23 @@ var queryMemoryTool = {
1995
2008
  - Provide context for conversations
1996
2009
  - Retrieve information for decision-making
1997
2010
  - Build responses using past knowledge
2011
+ - Find memories by concept rather than exact keywords
1998
2012
 
1999
2013
  Examples:
2000
2014
  - "What do I know about camping?"
2001
2015
  - "Tell me about the recipes I've saved"
2002
2016
  - "What meetings did I have last week?"
2003
2017
  - "What are my project goals?"
2018
+
2019
+ **AGENT GUIDANCE**:
2020
+ - If query results are too broad or include irrelevant content, try remember_search_memory instead - it uses hybrid search with keyword matching which is better for precise, specific searches. You can inform the user: "The results were too broad. Let me try a more precise keyword search using the search tool."
2021
+ - **CRITICAL**: If no results are returned, DO NOT make up or fabricate memories. Only report what was actually found. Tell the user honestly that no matching memories were found and suggest they:
2022
+ * Create a new memory with the information they're looking for
2023
+ * Try the other search tool (remember_search_memory for more precise keyword-based search)
2024
+ * Remove or relax filters if they applied any
2025
+ * Increase the limit parameter to see more results
2026
+ * Lower the min_relevance threshold to include less relevant matches
2027
+ * Try rephrasing the query with different terms
2004
2028
  `,
2005
2029
  inputSchema: {
2006
2030
  type: "object",
package/dist/server.js CHANGED
@@ -1475,6 +1475,8 @@ var searchMemoryTool = {
1475
1475
  name: "remember_search_memory",
1476
1476
  description: `Search memories AND relationships using hybrid semantic and keyword search.
1477
1477
 
1478
+ **BEST FOR**: Precise searches with specific keywords or exact phrases. Good for finding specific items when you know what you're looking for.
1479
+
1478
1480
  By default, searches BOTH memories and relationships to provide comprehensive results.
1479
1481
  Relationships contain valuable context in their observations.
1480
1482
 
@@ -1489,6 +1491,15 @@ var searchMemoryTool = {
1489
1491
  - "Find memories about camping trips" \u2192 returns memories + relationships about camping
1490
1492
  - "Search for recipes I saved" \u2192 returns recipe memories + related relationships
1491
1493
  - "Show me notes from last week" \u2192 returns notes + any relationships created that week
1494
+
1495
+ **AGENT GUIDANCE**:
1496
+ - If search results are too narrow or miss relevant content, try remember_query_memory instead - it uses pure semantic search which is better for broader, concept-based queries. You can inform the user: "I didn't find what you're looking for with keyword search. Let me try a broader semantic search using the query tool."
1497
+ - **CRITICAL**: If no results are returned, DO NOT make up or fabricate memories. Only report what was actually found. Tell the user honestly that no matching memories were found and suggest they:
1498
+ * Create a new memory with the information they're looking for
1499
+ * Try the other search tool (remember_query_memory for broader semantic search)
1500
+ * Remove or relax filters if they applied any
1501
+ * Increase the limit parameter to see more results
1502
+ * Try different search terms or keywords
1492
1503
  `,
1493
1504
  inputSchema: {
1494
1505
  type: "object",
@@ -2029,6 +2040,8 @@ var queryMemoryTool = {
2029
2040
  name: "remember_query_memory",
2030
2041
  description: `Query memories using natural language for RAG (Retrieval-Augmented Generation).
2031
2042
 
2043
+ **BEST FOR**: Broad, concept-based searches and natural language questions. Uses pure semantic search to find memories by meaning, not just keywords. Great for exploratory queries and when you're not sure of exact terms.
2044
+
2032
2045
  This tool is optimized for LLM context retrieval. It returns relevant memories
2033
2046
  with their full content and context, formatted for easy consumption by LLMs.
2034
2047
 
@@ -2037,12 +2050,23 @@ var queryMemoryTool = {
2037
2050
  - Provide context for conversations
2038
2051
  - Retrieve information for decision-making
2039
2052
  - Build responses using past knowledge
2053
+ - Find memories by concept rather than exact keywords
2040
2054
 
2041
2055
  Examples:
2042
2056
  - "What do I know about camping?"
2043
2057
  - "Tell me about the recipes I've saved"
2044
2058
  - "What meetings did I have last week?"
2045
2059
  - "What are my project goals?"
2060
+
2061
+ **AGENT GUIDANCE**:
2062
+ - If query results are too broad or include irrelevant content, try remember_search_memory instead - it uses hybrid search with keyword matching which is better for precise, specific searches. You can inform the user: "The results were too broad. Let me try a more precise keyword search using the search tool."
2063
+ - **CRITICAL**: If no results are returned, DO NOT make up or fabricate memories. Only report what was actually found. Tell the user honestly that no matching memories were found and suggest they:
2064
+ * Create a new memory with the information they're looking for
2065
+ * Try the other search tool (remember_search_memory for more precise keyword-based search)
2066
+ * Remove or relax filters if they applied any
2067
+ * Increase the limit parameter to see more results
2068
+ * Lower the min_relevance threshold to include less relevant matches
2069
+ * Try rephrasing the query with different terms
2046
2070
  `,
2047
2071
  inputSchema: {
2048
2072
  type: "object",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@prmichaelsen/remember-mcp",
3
- "version": "2.1.0",
3
+ "version": "2.2.1",
4
4
  "description": "Multi-tenant memory system MCP server with vector search and relationships",
5
5
  "main": "dist/server.js",
6
6
  "type": "module",
@@ -16,6 +16,8 @@ export const queryMemoryTool = {
16
16
  name: 'remember_query_memory',
17
17
  description: `Query memories using natural language for RAG (Retrieval-Augmented Generation).
18
18
 
19
+ **BEST FOR**: Broad, concept-based searches and natural language questions. Uses pure semantic search to find memories by meaning, not just keywords. Great for exploratory queries and when you're not sure of exact terms.
20
+
19
21
  This tool is optimized for LLM context retrieval. It returns relevant memories
20
22
  with their full content and context, formatted for easy consumption by LLMs.
21
23
 
@@ -24,12 +26,23 @@ export const queryMemoryTool = {
24
26
  - Provide context for conversations
25
27
  - Retrieve information for decision-making
26
28
  - Build responses using past knowledge
29
+ - Find memories by concept rather than exact keywords
27
30
 
28
31
  Examples:
29
32
  - "What do I know about camping?"
30
33
  - "Tell me about the recipes I've saved"
31
34
  - "What meetings did I have last week?"
32
35
  - "What are my project goals?"
36
+
37
+ **AGENT GUIDANCE**:
38
+ - If query results are too broad or include irrelevant content, try remember_search_memory instead - it uses hybrid search with keyword matching which is better for precise, specific searches. You can inform the user: "The results were too broad. Let me try a more precise keyword search using the search tool."
39
+ - **CRITICAL**: If no results are returned, DO NOT make up or fabricate memories. Only report what was actually found. Tell the user honestly that no matching memories were found and suggest they:
40
+ * Create a new memory with the information they're looking for
41
+ * Try the other search tool (remember_search_memory for more precise keyword-based search)
42
+ * Remove or relax filters if they applied any
43
+ * Increase the limit parameter to see more results
44
+ * Lower the min_relevance threshold to include less relevant matches
45
+ * Try rephrasing the query with different terms
33
46
  `,
34
47
  inputSchema: {
35
48
  type: 'object',
@@ -16,6 +16,8 @@ export const searchMemoryTool = {
16
16
  name: 'remember_search_memory',
17
17
  description: `Search memories AND relationships using hybrid semantic and keyword search.
18
18
 
19
+ **BEST FOR**: Precise searches with specific keywords or exact phrases. Good for finding specific items when you know what you're looking for.
20
+
19
21
  By default, searches BOTH memories and relationships to provide comprehensive results.
20
22
  Relationships contain valuable context in their observations.
21
23
 
@@ -30,6 +32,15 @@ export const searchMemoryTool = {
30
32
  - "Find memories about camping trips" → returns memories + relationships about camping
31
33
  - "Search for recipes I saved" → returns recipe memories + related relationships
32
34
  - "Show me notes from last week" → returns notes + any relationships created that week
35
+
36
+ **AGENT GUIDANCE**:
37
+ - If search results are too narrow or miss relevant content, try remember_query_memory instead - it uses pure semantic search which is better for broader, concept-based queries. You can inform the user: "I didn't find what you're looking for with keyword search. Let me try a broader semantic search using the query tool."
38
+ - **CRITICAL**: If no results are returned, DO NOT make up or fabricate memories. Only report what was actually found. Tell the user honestly that no matching memories were found and suggest they:
39
+ * Create a new memory with the information they're looking for
40
+ * Try the other search tool (remember_query_memory for broader semantic search)
41
+ * Remove or relax filters if they applied any
42
+ * Increase the limit parameter to see more results
43
+ * Try different search terms or keywords
33
44
  `,
34
45
  inputSchema: {
35
46
  type: 'object',