Skip to main content
Glama

forget

Remove specific memories from AI systems by ID to manage stored information and correct persistent data.

Instructions

Delete a memory by ID.

Args:
    memory_id: The memory to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The MCP tool registration and handler for 'forget'.
    @mcp.tool()
    def forget(memory_id: int) -> str:
        """Delete a memory by ID.
    
        Args:
            memory_id: The memory to delete.
        """
        mem = _get_mem()
        if mem.forget(memory_id):
            return f"Memory #{memory_id} deleted."
        return f"Memory #{memory_id} not found."
  • The underlying implementation of memory deletion in the Memory class.
    def forget(self, memory_id: int) -> bool:
        """Delete a memory by ID. Returns True if it existed."""
        return self.db.delete(memory_id)
Behavior2/5

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

With no annotations provided, the description carries the full burden of disclosure. It states 'Delete' but fails to specify whether this is permanent, if confirmation is required, what the return value indicates (despite output schema existing), or any side effects on related memories.

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?

Extremely efficient: front-loaded purpose statement followed by an Args docstring block. No redundant text; every element serves a functional purpose for a single-parameter tool.

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

Completeness3/5

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

Adequate for a simple 1-parameter tool with an output schema (so return values need not be explained), but incomplete given zero annotations and the destructive nature of the operation—lacks warnings or behavioral context that would make it fully self-contained.

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

Parameters4/5

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

Schema description coverage is 0% (property lacks description field), so the description compensates by documenting the parameter in the Args block: 'memory_id: The memory to delete.' While minimal, this successfully conveys the parameter's purpose beyond the schema's title 'Memory Id' and type 'integer'.

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

Purpose5/5

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

Clear specific verb (Delete) + resource (memory) + scope (by ID). Effectively distinguishes from sibling tools like 'recall' (retrieve), 'store' (create), and 'check' (verify) through its explicit destructive intent.

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 explicit guidance provided on when to use versus alternatives (e.g., when to delete vs. update/correct), no warnings about irreversibility, and no prerequisites mentioned despite being a destructive operation.

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/WeberG619/neveronce'

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