@prmichaelsen/remember-mcp 2.6.2 → 2.6.4

package/dist/server-factory.js

@@ -565,6 +565,34 @@ function sanitizeUserId(userId) {
 function getMemoryCollectionName(userId) {
   return `Memory_${sanitizeUserId(userId)}`;
 }
+var ALL_MEMORY_PROPERTIES = [
+  "user_id",
+  "doc_type",
+  "type",
+  "title",
+  "content",
+  "tags",
+  "weight",
+  "base_weight",
+  "trust_level",
+  "context",
+  "location",
+  "relationships",
+  "created_at",
+  "updated_at",
+  "version",
+  "attribution",
+  "source_url",
+  "author",
+  "parent_id",
+  "thread_root_id",
+  "moderation_flags"
+];
+async function fetchMemoryWithAllProperties(collection, memoryId) {
+  return await collection.query.fetchObjectById(memoryId, {
+    returnProperties: ALL_MEMORY_PROPERTIES
+  });
+}
 
 // src/firestore/init.ts
 init_config();
@@ -1542,6 +1570,11 @@ var searchMemoryTool = {
   - "Show me notes from last week" \u2192 returns notes + any relationships created that week
   
   **AGENT GUIDANCE**:
+  - \u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add filters.types unless the user explicitly requests filtering by content type.
+    * \u2705 CORRECT: User says "search for hiking" \u2192 { query: "hiking" }
+    * \u274C WRONG: User says "search for hiking" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * \u2705 CORRECT: User says "search for note memories about hiking" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * Let the search algorithm find ALL relevant memories regardless of type unless explicitly requested.
   - 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."
   - **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:
     * Create a new memory with the information they're looking for
@@ -2112,6 +2145,11 @@ var queryMemoryTool = {
   - "What are my project goals?"
   
   **AGENT GUIDANCE**:
+  - \u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add filters.types unless the user explicitly requests filtering by content type.
+    * \u2705 CORRECT: User says "what do I know about hiking?" \u2192 { query: "hiking" }
+    * \u274C WRONG: User says "what do I know about hiking?" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * \u2705 CORRECT: User says "what notes do I have about hiking?" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * Let the query algorithm find ALL relevant memories regardless of type unless explicitly requested.
   - 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."
   - **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:
     * Create a new memory with the information they're looking for
@@ -3833,11 +3871,15 @@ async function handlePublish(args, userId) {
       memoryId: args.memory_id
     });
     const userCollection = weaviateClient.collections.get(collectionName);
-    const memory = await userCollection.query.fetchObjectById(args.memory_id);
+    const memory = await fetchMemoryWithAllProperties(userCollection, args.memory_id);
     logger.debug("Memory fetch result", {
       tool: "remember_publish",
       found: !!memory,
-      memoryId: args.memory_id
+      memoryId: args.memory_id,
+      hasProperties: !!memory?.properties,
+      propertyCount: memory?.properties ? Object.keys(memory.properties).length : 0,
+      hasTitle: !!memory?.properties?.title,
+      hasContent: !!memory?.properties?.content
     });
     if (!memory) {
       logger.info("Memory not found", {
@@ -4024,13 +4066,18 @@ async function executePublishMemory(request, userId) {
       collectionName: getMemoryCollectionName(userId),
       memoryId: request.payload.memory_id
     });
-    const originalMemory = await userCollection.query.fetchObjectById(
+    const originalMemory = await fetchMemoryWithAllProperties(
+      userCollection,
       request.payload.memory_id
     );
     logger.debug("Original memory fetch result", {
       function: "executePublishMemory",
       found: !!originalMemory,
-      memoryId: request.payload.memory_id
+      memoryId: request.payload.memory_id,
+      hasProperties: !!originalMemory?.properties,
+      propertyCount: originalMemory?.properties ? Object.keys(originalMemory.properties).length : 0,
+      hasTitle: !!originalMemory?.properties?.title,
+      hasContent: !!originalMemory?.properties?.content
     });
     if (!originalMemory) {
       logger.info("Original memory not found", {
@@ -4186,7 +4233,14 @@ import { Filters as Filters3 } from "weaviate-client";
 init_space_memory();
 var searchSpaceTool = {
   name: "remember_search_space",
-  description: "Search one or more shared spaces to discover thoughts, ideas, and memories. By default, excludes comments to keep discovery clean. Set include_comments: true to include threaded discussions. Can search multiple spaces in a single query.",
+  description: `Search one or more shared spaces to discover thoughts, ideas, and memories. By default, excludes comments to keep discovery clean. Set include_comments: true to include threaded discussions. Can search multiple spaces in a single query.
+
+\u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add content_type filter unless the user explicitly requests filtering by type.
+- \u2705 CORRECT: User says "search The Void for hiking" \u2192 { spaces: ["the_void"], query: "hiking" }
+- \u274C WRONG: User says "search The Void for hiking" \u2192 { spaces: ["the_void"], query: "hiking", content_type: "note" }
+- \u2705 CORRECT: User says "search The Void for note memories about hiking" \u2192 { spaces: ["the_void"], query: "hiking", content_type: "note" }
+
+Let the search algorithm find ALL relevant memories regardless of type unless explicitly requested.`,
   inputSchema: {
     type: "object",
     properties: {
@@ -4345,7 +4399,14 @@ import { Filters as Filters4 } from "weaviate-client";
 init_space_memory();
 var querySpaceTool = {
   name: "remember_query_space",
-  description: "Ask natural language questions about memories in shared spaces. By default, excludes comments to focus on original content. Set include_comments: true to include discussions in answers.",
+  description: `Ask natural language questions about memories in shared spaces. By default, excludes comments to focus on original content. Set include_comments: true to include discussions in answers.
+
+\u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add content_type filter unless the user explicitly requests filtering by type.
+- \u2705 CORRECT: User says "what's in The Void about hiking?" \u2192 { spaces: ["the_void"], question: "hiking" }
+- \u274C WRONG: User says "what's in The Void about hiking?" \u2192 { spaces: ["the_void"], question: "hiking", content_type: "note" }
+- \u2705 CORRECT: User says "what notes are in The Void about hiking?" \u2192 { spaces: ["the_void"], question: "hiking", content_type: "note" }
+
+Let the query algorithm find ALL relevant memories regardless of type unless explicitly requested.`,
   inputSchema: {
     type: "object",
     properties: {

package/dist/server.js

@@ -611,6 +611,34 @@ function sanitizeUserId(userId) {
 function getMemoryCollectionName(userId) {
   return `Memory_${sanitizeUserId(userId)}`;
 }
+var ALL_MEMORY_PROPERTIES = [
+  "user_id",
+  "doc_type",
+  "type",
+  "title",
+  "content",
+  "tags",
+  "weight",
+  "base_weight",
+  "trust_level",
+  "context",
+  "location",
+  "relationships",
+  "created_at",
+  "updated_at",
+  "version",
+  "attribution",
+  "source_url",
+  "author",
+  "parent_id",
+  "thread_root_id",
+  "moderation_flags"
+];
+async function fetchMemoryWithAllProperties(collection, memoryId) {
+  return await collection.query.fetchObjectById(memoryId, {
+    returnProperties: ALL_MEMORY_PROPERTIES
+  });
+}
 
 // src/firestore/init.ts
 init_config();
@@ -1610,6 +1638,11 @@ var searchMemoryTool = {
   - "Show me notes from last week" \u2192 returns notes + any relationships created that week
   
   **AGENT GUIDANCE**:
+  - \u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add filters.types unless the user explicitly requests filtering by content type.
+    * \u2705 CORRECT: User says "search for hiking" \u2192 { query: "hiking" }
+    * \u274C WRONG: User says "search for hiking" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * \u2705 CORRECT: User says "search for note memories about hiking" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * Let the search algorithm find ALL relevant memories regardless of type unless explicitly requested.
   - 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."
   - **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:
     * Create a new memory with the information they're looking for
@@ -2180,6 +2213,11 @@ var queryMemoryTool = {
   - "What are my project goals?"
   
   **AGENT GUIDANCE**:
+  - \u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add filters.types unless the user explicitly requests filtering by content type.
+    * \u2705 CORRECT: User says "what do I know about hiking?" \u2192 { query: "hiking" }
+    * \u274C WRONG: User says "what do I know about hiking?" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * \u2705 CORRECT: User says "what notes do I have about hiking?" \u2192 { query: "hiking", filters: { types: ["note"] } }
+    * Let the query algorithm find ALL relevant memories regardless of type unless explicitly requested.
   - 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."
   - **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:
     * Create a new memory with the information they're looking for
@@ -3901,11 +3939,15 @@ async function handlePublish(args, userId) {
       memoryId: args.memory_id
     });
     const userCollection = weaviateClient.collections.get(collectionName);
-    const memory = await userCollection.query.fetchObjectById(args.memory_id);
+    const memory = await fetchMemoryWithAllProperties(userCollection, args.memory_id);
     logger.debug("Memory fetch result", {
       tool: "remember_publish",
       found: !!memory,
-      memoryId: args.memory_id
+      memoryId: args.memory_id,
+      hasProperties: !!memory?.properties,
+      propertyCount: memory?.properties ? Object.keys(memory.properties).length : 0,
+      hasTitle: !!memory?.properties?.title,
+      hasContent: !!memory?.properties?.content
     });
     if (!memory) {
       logger.info("Memory not found", {
@@ -4092,13 +4134,18 @@ async function executePublishMemory(request, userId) {
       collectionName: getMemoryCollectionName(userId),
       memoryId: request.payload.memory_id
     });
-    const originalMemory = await userCollection.query.fetchObjectById(
+    const originalMemory = await fetchMemoryWithAllProperties(
+      userCollection,
       request.payload.memory_id
     );
     logger.debug("Original memory fetch result", {
       function: "executePublishMemory",
       found: !!originalMemory,
-      memoryId: request.payload.memory_id
+      memoryId: request.payload.memory_id,
+      hasProperties: !!originalMemory?.properties,
+      propertyCount: originalMemory?.properties ? Object.keys(originalMemory.properties).length : 0,
+      hasTitle: !!originalMemory?.properties?.title,
+      hasContent: !!originalMemory?.properties?.content
     });
     if (!originalMemory) {
       logger.info("Original memory not found", {
@@ -4254,7 +4301,14 @@ import { Filters as Filters3 } from "weaviate-client";
 init_space_memory();
 var searchSpaceTool = {
   name: "remember_search_space",
-  description: "Search one or more shared spaces to discover thoughts, ideas, and memories. By default, excludes comments to keep discovery clean. Set include_comments: true to include threaded discussions. Can search multiple spaces in a single query.",
+  description: `Search one or more shared spaces to discover thoughts, ideas, and memories. By default, excludes comments to keep discovery clean. Set include_comments: true to include threaded discussions. Can search multiple spaces in a single query.
+
+\u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add content_type filter unless the user explicitly requests filtering by type.
+- \u2705 CORRECT: User says "search The Void for hiking" \u2192 { spaces: ["the_void"], query: "hiking" }
+- \u274C WRONG: User says "search The Void for hiking" \u2192 { spaces: ["the_void"], query: "hiking", content_type: "note" }
+- \u2705 CORRECT: User says "search The Void for note memories about hiking" \u2192 { spaces: ["the_void"], query: "hiking", content_type: "note" }
+
+Let the search algorithm find ALL relevant memories regardless of type unless explicitly requested.`,
   inputSchema: {
     type: "object",
     properties: {
@@ -4413,7 +4467,14 @@ import { Filters as Filters4 } from "weaviate-client";
 init_space_memory();
 var querySpaceTool = {
   name: "remember_query_space",
-  description: "Ask natural language questions about memories in shared spaces. By default, excludes comments to focus on original content. Set include_comments: true to include discussions in answers.",
+  description: `Ask natural language questions about memories in shared spaces. By default, excludes comments to focus on original content. Set include_comments: true to include discussions in answers.
+
+\u26A0\uFE0F **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add content_type filter unless the user explicitly requests filtering by type.
+- \u2705 CORRECT: User says "what's in The Void about hiking?" \u2192 { spaces: ["the_void"], question: "hiking" }
+- \u274C WRONG: User says "what's in The Void about hiking?" \u2192 { spaces: ["the_void"], question: "hiking", content_type: "note" }
+- \u2705 CORRECT: User says "what notes are in The Void about hiking?" \u2192 { spaces: ["the_void"], question: "hiking", content_type: "note" }
+
+Let the query algorithm find ALL relevant memories regardless of type unless explicitly requested.`,
   inputSchema: {
     type: "object",
     properties: {

package/dist/weaviate/client.d.ts

@@ -33,6 +33,22 @@ export declare function getTemplateCollectionName(userId: string): string;
  * Get collection name for user's audit logs
  */
 export declare function getAuditCollectionName(userId: string): string;
+/**
+ * List of all memory properties to fetch
+ * Centralized to ensure consistency across all tools
+ */
+export declare const ALL_MEMORY_PROPERTIES: readonly ["user_id", "doc_type", "type", "title", "content", "tags", "weight", "base_weight", "trust_level", "context", "location", "relationships", "created_at", "updated_at", "version", "attribution", "source_url", "author", "parent_id", "thread_root_id", "moderation_flags"];
+/**
+ * Fetch a memory object by ID with all properties
+ *
+ * This utility ensures all memory properties are fetched consistently
+ * across all tools, preventing bugs where properties are missing.
+ *
+ * @param collection - Weaviate collection
+ * @param memoryId - Memory ID to fetch
+ * @returns Memory object with all properties
+ */
+export declare function fetchMemoryWithAllProperties(collection: any, memoryId: string): Promise<any>;
 /**
  * Check if collection exists
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@prmichaelsen/remember-mcp",
-  "version": "2.6.2",
+  "version": "2.6.4",
   "description": "Multi-tenant memory system MCP server with vector search and relationships",
   "main": "dist/server.js",
   "type": "module",

package/src/tools/confirm.ts

@@ -7,7 +7,7 @@
 
 import type { Tool } from '@modelcontextprotocol/sdk/types.js';
 import { confirmationTokenService, type ConfirmationRequest } from '../services/confirmation-token.service.js';
-import { getWeaviateClient, getMemoryCollectionName } from '../weaviate/client.js';
+import { getWeaviateClient, getMemoryCollectionName, fetchMemoryWithAllProperties } from '../weaviate/client.js';
 import { ensurePublicCollection } from '../weaviate/space-schema.js';
 import { handleToolError } from '../utils/error-handler.js';
 import { logger } from '../utils/logger.js';
@@ -151,7 +151,8 @@ async function executePublishMemory(
       memoryId: request.payload.memory_id,
     });
 
-    const originalMemory = await userCollection.query.fetchObjectById(
+    const originalMemory = await fetchMemoryWithAllProperties(
+      userCollection,
       request.payload.memory_id
     );
     
@@ -159,6 +160,10 @@ async function executePublishMemory(
       function: 'executePublishMemory',
       found: !!originalMemory,
       memoryId: request.payload.memory_id,
+      hasProperties: !!originalMemory?.properties,
+      propertyCount: originalMemory?.properties ? Object.keys(originalMemory.properties).length : 0,
+      hasTitle: !!originalMemory?.properties?.title,
+      hasContent: !!originalMemory?.properties?.content,
     });
 
     if (!originalMemory) {

package/src/tools/publish.ts

@@ -7,7 +7,7 @@
 
 import type { Tool } from '@modelcontextprotocol/sdk/types.js';
 import { confirmationTokenService } from '../services/confirmation-token.service.js';
-import { getWeaviateClient, getMemoryCollectionName } from '../weaviate/client.js';
+import { getWeaviateClient, getMemoryCollectionName, fetchMemoryWithAllProperties } from '../weaviate/client.js';
 import { isValidSpaceId } from '../weaviate/space-schema.js';
 import { handleToolError } from '../utils/error-handler.js';
 import { SUPPORTED_SPACES } from '../types/space-memory.js';
@@ -122,12 +122,16 @@ export async function handlePublish(
     
     const userCollection = weaviateClient.collections.get(collectionName);
 
-    const memory = await userCollection.query.fetchObjectById(args.memory_id);
+    const memory = await fetchMemoryWithAllProperties(userCollection, args.memory_id);
     
     logger.debug('Memory fetch result', {
       tool: 'remember_publish',
       found: !!memory,
       memoryId: args.memory_id,
+      hasProperties: !!memory?.properties,
+      propertyCount: memory?.properties ? Object.keys(memory.properties).length : 0,
+      hasTitle: !!memory?.properties?.title,
+      hasContent: !!memory?.properties?.content,
     });
 
     if (!memory) {

package/src/tools/query-memory.ts

@@ -35,6 +35,11 @@ export const queryMemoryTool = {
   - "What are my project goals?"
   
   **AGENT GUIDANCE**:
+  - ⚠️ **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add filters.types unless the user explicitly requests filtering by content type.
+    * ✅ CORRECT: User says "what do I know about hiking?" → { query: "hiking" }
+    * ❌ WRONG: User says "what do I know about hiking?" → { query: "hiking", filters: { types: ["note"] } }
+    * ✅ CORRECT: User says "what notes do I have about hiking?" → { query: "hiking", filters: { types: ["note"] } }
+    * Let the query algorithm find ALL relevant memories regardless of type unless explicitly requested.
   - 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."
   - **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:
     * Create a new memory with the information they're looking for

package/src/tools/query-space.ts

@@ -17,7 +17,14 @@ import { handleToolError } from '../utils/error-handler.js';
  */
 export const querySpaceTool: Tool = {
   name: 'remember_query_space',
-  description: 'Ask natural language questions about memories in shared spaces. By default, excludes comments to focus on original content. Set include_comments: true to include discussions in answers.',
+  description: `Ask natural language questions about memories in shared spaces. By default, excludes comments to focus on original content. Set include_comments: true to include discussions in answers.
+
+⚠️ **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add content_type filter unless the user explicitly requests filtering by type.
+- ✅ CORRECT: User says "what's in The Void about hiking?" → { spaces: ["the_void"], question: "hiking" }
+- ❌ WRONG: User says "what's in The Void about hiking?" → { spaces: ["the_void"], question: "hiking", content_type: "note" }
+- ✅ CORRECT: User says "what notes are in The Void about hiking?" → { spaces: ["the_void"], question: "hiking", content_type: "note" }
+
+Let the query algorithm find ALL relevant memories regardless of type unless explicitly requested.`,
   inputSchema: {
     type: 'object',
     properties: {

package/src/tools/search-memory.ts

@@ -34,6 +34,11 @@ export const searchMemoryTool = {
   - "Show me notes from last week" → returns notes + any relationships created that week
   
   **AGENT GUIDANCE**:
+  - ⚠️ **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add filters.types unless the user explicitly requests filtering by content type.
+    * ✅ CORRECT: User says "search for hiking" → { query: "hiking" }
+    * ❌ WRONG: User says "search for hiking" → { query: "hiking", filters: { types: ["note"] } }
+    * ✅ CORRECT: User says "search for note memories about hiking" → { query: "hiking", filters: { types: ["note"] } }
+    * Let the search algorithm find ALL relevant memories regardless of type unless explicitly requested.
   - 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."
   - **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:
     * Create a new memory with the information they're looking for

package/src/tools/search-space.ts

@@ -18,7 +18,14 @@ import type { SearchFilters } from '../types/memory.js';
  */
 export const searchSpaceTool: Tool = {
   name: 'remember_search_space',
-  description: 'Search one or more shared spaces to discover thoughts, ideas, and memories. By default, excludes comments to keep discovery clean. Set include_comments: true to include threaded discussions. Can search multiple spaces in a single query.',
+  description: `Search one or more shared spaces to discover thoughts, ideas, and memories. By default, excludes comments to keep discovery clean. Set include_comments: true to include threaded discussions. Can search multiple spaces in a single query.
+
+⚠️ **CRITICAL - CONTENT TYPE FILTERING**: Do NOT add content_type filter unless the user explicitly requests filtering by type.
+- ✅ CORRECT: User says "search The Void for hiking" → { spaces: ["the_void"], query: "hiking" }
+- ❌ WRONG: User says "search The Void for hiking" → { spaces: ["the_void"], query: "hiking", content_type: "note" }
+- ✅ CORRECT: User says "search The Void for note memories about hiking" → { spaces: ["the_void"], query: "hiking", content_type: "note" }
+
+Let the search algorithm find ALL relevant memories regardless of type unless explicitly requested.`,
   inputSchema: {
     type: 'object',
     properties: {

package/src/weaviate/client.ts

@@ -139,6 +139,53 @@ export function getAuditCollectionName(userId: string): string {
   return `Audit_${sanitizeUserId(userId)}`;
 }
 
+/**
+ * List of all memory properties to fetch
+ * Centralized to ensure consistency across all tools
+ */
+export const ALL_MEMORY_PROPERTIES = [
+  'user_id',
+  'doc_type',
+  'type',
+  'title',
+  'content',
+  'tags',
+  'weight',
+  'base_weight',
+  'trust_level',
+  'context',
+  'location',
+  'relationships',
+  'created_at',
+  'updated_at',
+  'version',
+  'attribution',
+  'source_url',
+  'author',
+  'parent_id',
+  'thread_root_id',
+  'moderation_flags',
+] as const;
+
+/**
+ * Fetch a memory object by ID with all properties
+ *
+ * This utility ensures all memory properties are fetched consistently
+ * across all tools, preventing bugs where properties are missing.
+ *
+ * @param collection - Weaviate collection
+ * @param memoryId - Memory ID to fetch
+ * @returns Memory object with all properties
+ */
+export async function fetchMemoryWithAllProperties(
+  collection: any,
+  memoryId: string
+) {
+  return await collection.query.fetchObjectById(memoryId, {
+    returnProperties: ALL_MEMORY_PROPERTIES,
+  });
+}
+
 /**
  * Check if collection exists
  */