Skip to main content
Glama

delete_memory

Delete a memory with two modes: soft-archive (reversible, sets weight=0 for audit) or hard-remove (permanent, erases row entirely).

Instructions

Delete a memory — soft (archive) or hard (permanent removal).

Two modes:

  • Soft-delete (default, permanent=False): sets weight=0. Memory stays in LanceDB for audit trail but never surfaces in recall. Reversible via update().

  • Hard-delete (permanent=True): removes the row from LanceDB entirely. Irreversible. The ID cannot be reused.

Read-only: no. Mutates or removes a row. Prefer forget() for routine archiving; reserve permanent=True for data that must be erased.

Args: id: Memory ID to delete. permanent: False = soft-delete (weight=0), True = remove row from LanceDB permanently. Default: False.

Returns: dict: {'ok': True, 'id': , 'action': 'soft_deleted'} or {'ok': True, 'id': , 'action': 'deleted_permanently'}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesMemory ID to delete.
permanentNoFalse = soft-delete (weight=0, reversible). True = permanent removal from LanceDB (irreversible).
Behavior5/5

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

No annotations were provided, but the description thoroughly discloses the tool's mutational behavior, irreversibility of hard delete, and the effect of both modes (setting weight=0 vs removing row). No contradiction with any structured data.

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?

Well-structured with clear sections (overview, modes, args, returns). Front-loaded with purpose and key distinction. Could trim minor redundancy (e.g., 'Read-only: no' is implied by 'mutates or removes a row') but overall efficient.

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?

Given only 2 parameters and no output schema, the description fully covers the tool: explains modes, parameters with defaults, return format, and usage guidance. No gaps remain for an agent to invoke correctly.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the default behavior of 'permanent', the reversibility note for soft-delete, and the context for each parameter beyond the schema comments.

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 explicitly states the tool deletes a memory with two modes (soft/hard), clearly identifying the verb and resource. It distinguishes itself from sibling tools like 'forget' and 'purge_memories' by detailing the deletion behavior and reversibility.

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?

Provides explicit guidance on when to use each mode: prefers 'forget' for routine archiving and reserves permanent=True for data that must be erased. Also notes reversibility of soft-delete.

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