Skip to main content
Glama
akaiserg

MCP Memory Tracker

by akaiserg

search_memories

Search through saved conversation memories using vector similarity to find relevant information from previous interactions.

Instructions

Search the vector store for memories that match the query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • server.py:39-58 (handler)
    The @mcp.tool() decorator registers the search_memories handler function, which performs a vector store search using OpenAI client and returns matching memory texts.
    @mcp.tool()
    def search_memories(query: str):
        """Search the vector store for memories that match the query."""
        vector_store = get_or_create_vector_store()
        print(vector_store.id)
        results = client.vector_stores.search(
            vector_store_id=vector_store.id,
            query=query,     
        )
        print(results)
        
        # Handle SyncPage response - iterate through the data
        content_text = []
        for item in results.data:
            if hasattr(item, 'content'):
                for content in item.content:
                    if content.type == "text":
                        content_text.append(content.text)
        
        return {"status": "success", "results": content_text}
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions searching a 'vector store' which hints at semantic matching, but doesn't disclose details like return format, pagination, error handling, or performance characteristics.

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

Conciseness5/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 and resource, making it easy to parse quickly.

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, no output schema, and low schema coverage, the description is incomplete. It lacks details on behavior, parameters, and expected results, making it inadequate for a tool that performs a non-trivial search operation.

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 little. It mentions 'query' but doesn't explain what constitutes a valid query (e.g., keywords, natural language), its format, or how matching works, leaving parameter meaning unclear.

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

Purpose4/5

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

The description clearly states the action ('Search') and resource ('vector store for memories'), making the purpose understandable. It doesn't explicitly distinguish from the sibling 'save_memory', but the verb 'Search' versus 'save' provides implicit differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives or in what context. It mentions 'match the query' but doesn't specify scenarios, prerequisites, or exclusions, leaving usage ambiguous.

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

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/akaiserg/mcp-memory-tracker'

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