Skip to main content
Glama

forget

Archive outdated or incorrect memories by setting their weight to zero, excluding them from recall results while preserving them for audit.

Instructions

Archive a memory by setting its weight to zero.

The memory row remains in LanceDB for audit but is excluded from all recall results (weight=0 → weight_score=0 → final_score=0). Use for outdated or incorrect memories. For permanent deletion use delete_memory with permanent=True. For bulk cleanup use purge_memories.

Read-only: no. Mutates the memory's weight to 0. Reversible via update() by setting weight back to a non-zero value.

Args: id: Memory ID (returned by remember() or recall()).

Returns: dict: {'ok': True, 'id': , 'action': 'forgotten'}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory ID to archive (returned by remember() or recall()).
Behavior5/5

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

Explains behavior: weight set to zero, remains in DB but excluded from recall results. States it's not read-only, mutates weight, reversible via update(). No annotations provided, so description carries full burden and does well.

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?

Front-loaded purpose, well-structured with sections. Some redundancy in Args vs schema, but overall efficient and clear.

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

Completeness5/5

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

With one parameter, no output schema, and no annotations, the description covers purpose, behavior, reversibility, return value, and usage alternatives. Complete for agent 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?

Schema coverage is 100%, and the description repeats the parameter info from schema. Adds no new meaning beyond schema's 'Memory ID to archive (returned by remember() or recall()).' Baseline 3 applies.

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?

The description clearly states 'Archive a memory by setting its weight to zero.' It specifies the verb (archive), resource (memory), and mechanism. It distinguishes from siblings like delete_memory and purge_memories.

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

Usage Guidelines5/5

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

Explicitly says 'Use for outdated or incorrect memories.' Provides alternatives for permanent deletion and bulk cleanup, guiding when not to use this tool.

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/turbyho/mem-context'

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