Skip to main content
Glama

forget

Delete a stored memory by its ID to remove outdated or unwanted information from an AI agent's long-term local memory.

Instructions

Delete one memory by its id (ids come from recall or list_memories).

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": {
      "memory_id": "<memory_id>"
    },
    "name": "forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
memory_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses only that this is a delete of exactly one memory; it says nothing about whether deletion is permanent, whether confirmation is required, what happens if the id does not exist, or what permissions are needed. For an irreversible mutation with zero annotation coverage, that is a substantial gap.

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?

One short sentence with the destructive action and its scope front-loaded, plus a tightly scoped parenthetical that earns its place by telling the agent where to get the required id. No redundant restatement of the tool name or filler.

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?

The tool is simple (one required integer, output schema present so returns need no explanation), and the description covers what it deletes and how to source the id. Because no annotations exist, it should also state irreversibility and error behavior for a missing id; those omissions leave it only minimally complete for a destructive operation.

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 0% and the sole parameter memory_id carries only a title, so the description must compensate. It does add genuine meaning by explaining that the id identifies a single memory and where ids originate (recall or list_memories), but it does not state the expected type or format of the id beyond what the schema already implies.

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 states a specific verb and resource with explicit scope: 'Delete one memory by its id.' That single-memory scope implicitly separates it from the plural/list siblings list_memories and recall, and the parenthetical ties it to those tools as id sources. It stops short of naming an alternative for any other operation, so it is clear but not fully self-differentiating.

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

Usage Guidelines4/5

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

The parenthetical '(ids come from recall or list_memories)' gives real prerequisite guidance: you must obtain an id from a retrieval tool before calling this. What is missing is any when-not guidance, such as handling a memory you are unsure about or what to do when the id is unknown.

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

Deploy Server

Other Tools