Skip to main content
Glama
drdee

Memory MCP

by drdee

remember

Store and organize information with structured titles and content using a SQLite-based memory storage system. Ideal for managing and retrieving data efficiently.

Instructions

Store a new memory.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe full content of the memory to store
titleYesA concise title for the memory

Implementation Reference

  • The core handler function that executes the 'remember' tool by storing the provided title and content in the database and returning a success message with the memory ID.
    def remember(title: str, content: str) -> str:
        """
        Store a new memory.
    
        Args:
            title: A concise title for the memory
            content: The full content of the memory to store
    
        Returns:
            A confirmation message with the ID of the stored memory
        """
        try:
            memory_id = db.add_memory(title, content)
            return f"Memory stored successfully with ID: {memory_id}."
        except Exception as e:
            return f"Error storing memory: {str(e)}"
  • The JSON schema defining the input parameters for the 'remember' tool: required 'title' and 'content' as strings.
    inputSchema={
        "type": "object",
        "properties": {
            "title": {
                "type": "string",
                "description": "A concise title for the memory",
            },
            "content": {
                "type": "string",
                "description": "The full content of the memory to store",
            },
        },
        "required": ["title", "content"],
        "title": "rememberArguments",
    },
  • The dispatch logic in the call_tool handler that registers and invokes the 'remember' tool when called.
    if name == "remember":
        if not arguments or "title" not in arguments or "content" not in arguments:
            raise ValueError("Missing title or content arguments")
        result = remember(arguments["title"], arguments["content"])
        return [types.TextContent(type="text", text=result)]
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Store a new memory' implies a write operation, but it doesn't specify whether this is idempotent, requires authentication, has side effects, or what happens on failure. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding its behavior.

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 ('Store a new memory') that is front-loaded and wastes no words. It directly conveys the core action without unnecessary elaboration, making it highly concise and well-structured.

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 that this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, potential errors, or how it interacts with sibling tools like 'list_memories'. For a tool that modifies state, more context is needed to guide effective usage.

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

Parameters3/5

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

The schema description coverage is 100%, with clear descriptions for both parameters ('content' and 'title'). The tool description adds no additional parameter information beyond what's in the schema, so it meets the baseline score of 3 where the schema does the heavy lifting without extra value from the description.

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 'Store a new memory' clearly states the verb ('store') and resource ('memory'), making the tool's purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'update_memory' or 'delete_memory' beyond the 'new' qualifier, which is why it doesn't reach the highest score.

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 like 'update_memory' or 'delete_memory'. It lacks any context about prerequisites, such as whether this creates a memory from scratch versus modifying existing ones, leaving the agent to infer usage from the tool name 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/drdee/memory-mcp'

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