Skip to main content
Glama

Forget a memory entry

forget

Delete a specific memory row by ID and sync the search index to remove outdated preferences, lessons, or interactions from local storage.

Instructions

Delete one memory row (preference, lesson or interaction) by id and sync the search index. Pass type when you know it (ids from remember are preference ids, from save_lesson are lesson ids).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "target_id": "<target_id>"
    },
    "name": "forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhich table the id belongs to. Recommended whenever known, because numeric ids can coincide across tables.
target_idYesRow id to delete (id returned by remember/save_lesson)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.4.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / target_id / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changedv2.2.9
    • changedInput schema / properties / type / enum
      Previous value: -[
      -  "preference",
      -  "lesson",
      -  "interaction"
      -]New value: +[
      +  "memory",
      +  "preference",
      +  "lesson",
      +  "interaction"
      +]
  3. First observedv2.2.1

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does say the operation deletes a row and syncs the search index, which is real behavioral context, but it doesn't state whether the delete is permanent, whether it requires confirmation, or what happens to data created by link_memory or merge_memory when a row disappears.

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?

Two sentences, both front-loaded and free of filler. The destructive action comes first and the parameter hint follows, so an agent can read the essentials immediately.

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?

For a destructive tool with no annotations and no output schema, the description covers what is deleted and the index-sync effect, but it says nothing about irreversibility, recovery, or side effects on related memory links. Enough to call it, not enough to call it safely.

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 the baseline is 3. The description still adds meaning by mapping id sources to the type enum ('remember' implies preference, 'save_lesson' implies lesson), which goes beyond the schema's generic note that ids can coincide across tables.

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 opens with a specific verb and resource: 'Delete one memory row (preference, lesson or interaction) by id'. It also mentions syncing the search index, which separates it from update_memory, merge_memory and link_memory among the siblings.

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

Usage Guidelines3/5

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

It gives useful calling context about id provenance ('ids from remember are preference ids, from save_lesson are lesson ids'), but that is parameter guidance rather than when-to-use guidance. Nothing says when to forget rather than update_memory, merge_memory or consolidate, and no prerequisite or irreversibility warning is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.