Skip to main content
Glama

retrieve_memory

Locate relevant stored information by querying the MCP Memory Service. Leverages ChromaDB and sentence transformers for accurate semantic search and retrieval.

Instructions

Find relevant memories based on query

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
n_resultsNo
queryYes

Implementation Reference

  • The primary MCP tool handler for 'retrieve_memory'. This function is decorated with @mcp.tool(), automatically registering it as an MCP tool. It accepts a semantic query and optional n_results parameter, delegating the core logic to MemoryService.retrieve_memories().
    async def retrieve_memory(
        query: str,
        ctx: Context,
        n_results: int = 5
    ) -> Dict[str, Any]:
        """
        Retrieve memories based on semantic similarity to a query.
    
        Args:
            query: Search query for semantic similarity
            n_results: Maximum number of results to return
    
        Returns:
            Dictionary with retrieved memories and metadata
        """
        # Delegate to shared MemoryService business logic
        memory_service = ctx.request_context.lifespan_context.memory_service
        return await memory_service.retrieve_memories(
            query=query,
            n_results=n_results
        )
  • The @mcp.tool() decorator registers the retrieve_memory function as an available MCP tool.
    async def retrieve_memory(
  • Core helper method in MemoryService that implements the semantic retrieval logic. Calls the storage backend's retrieve() method, applies optional filters, formats results with relevance scores, and handles errors.
    async def retrieve_memories(
        self,
        query: str,
        n_results: int = 10,
        tags: Optional[List[str]] = None,
        memory_type: Optional[str] = None
    ) -> Union[RetrieveMemoriesSuccess, RetrieveMemoriesError]:
        """
        Retrieve memories by semantic search with optional filtering.
    
        Args:
            query: Search query string
            n_results: Maximum number of results
            tags: Optional tag filtering
            memory_type: Optional memory type filtering
    
        Returns:
            Dictionary with search results
        """
        try:
            # Retrieve memories using semantic search
            # Note: storage.retrieve() only supports query and n_results
            # We'll filter by tags/type after retrieval if needed
            memories = await self.storage.retrieve(
                query=query,
                n_results=n_results
            )
    
            # Apply optional post-filtering
            filtered_memories = memories
            if tags or memory_type:
                filtered_memories = []
                for memory in memories:
                    # Filter by tags if specified
                    if tags:
                        memory_tags = memory.metadata.get('tags', []) if hasattr(memory, 'metadata') else []
                        if not any(tag in memory_tags for tag in tags):
                            continue
    
                    # Filter by memory_type if specified
                    if memory_type:
                        mem_type = memory.metadata.get('memory_type', '') if hasattr(memory, 'metadata') else ''
                        if mem_type != memory_type:
                            continue
    
                    filtered_memories.append(memory)
    
            results = []
            for result in filtered_memories:
                # Extract Memory object from MemoryQueryResult and add similarity score
                memory_dict = self._format_memory_response(result.memory)
                memory_dict['similarity_score'] = result.relevance_score
                results.append(memory_dict)
    
            return {
                "memories": results,
                "query": query,
                "count": len(results)
            }
    
        except Exception as e:
            logger.error(f"Error retrieving memories: {e}")
            return {
                "memories": [],
                "query": query,
                "error": f"Failed to retrieve memories: {str(e)}"
            }
  • Input schema defined by function parameters: required 'query' (str), optional 'n_results' (int, default 5). Output is Dict[str, Any] containing memories list with metadata and scores.
        query: str,
        ctx: Context,
        n_results: int = 5
    ) -> Dict[str, Any]:
        """
        Retrieve memories based on semantic similarity to a query.
    
        Args:
            query: Search query for semantic similarity
            n_results: Maximum number of results to return
    
        Returns:
            Dictionary with retrieved memories and metadata
        """
        # Delegate to shared MemoryService business logic
        memory_service = ctx.request_context.lifespan_context.memory_service
        return await memory_service.retrieve_memories(
            query=query,
            n_results=n_results
        )
    
    @mcp.tool()
    async def search_by_tag(
        tags: Union[str, List[str]],
        ctx: Context,
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden but provides minimal behavioral context. It mentions 'find relevant memories' but doesn't disclose how relevance is scored, whether results are paginated, if there are rate limits, authentication needs, or what happens on failure. The description lacks details needed for safe and effective use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded with the core action ('Find relevant memories'), though it could be more structured with additional context. For its brevity, it communicates the essence without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, 0% schema coverage, no output schema, and two parameters, the description is incomplete. It doesn't explain what 'memories' are, how they're retrieved, the return format, or error handling. For a tool with query and result-limit parameters, more context is needed for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate but adds no parameter-specific information. It mentions 'query' generally but doesn't explain its format, constraints, or how 'n_results' affects output. The description fails to clarify semantics beyond the bare schema, leaving parameters poorly understood.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Find relevant memories based on query' states the general purpose (verb 'find' + resource 'memories') but lacks specificity about what 'memories' are or how relevance is determined. It distinguishes from 'store_memory' but not clearly from 'search_by_tag' (both involve finding memories). The purpose is understandable but vague.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives like 'search_by_tag'. The description implies usage for query-based retrieval, but there's no explicit mention of when-not-to-use, prerequisites, or comparison with siblings. Usage is implied from the name and description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/doobidoo/mcp-memory-service'

If you have feedback or need assistance with the MCP directory API, please join our Discord server