Skip to main content
Glama

forget

Deletes stale or wrong memories by memory id or search query. Confident matches are removed immediately; otherwise candidates are listed to choose an explicit id.

Instructions

Delete a stale or wrong memory. Pass the memory id for a direct delete, or a query: a confident match is deleted immediately, otherwise candidates are listed for you to pick an explicit id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
idNoMemory id (direct delete)
queryNoKeywords to find the memory to forget

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 burden. It usefully discloses that a confident query match is deleted immediately and that otherwise candidates are returned, which is important destructive behavior. However, it omits irreversibility, permission requirements, and whether confirmation is possible before deletion.

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 compact sentences with no wasted wording. The destructive action and the direct-versus-query branching are front-loaded and easy to parse.

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 mutation tool with no annotations and no output schema, missing details matter. The description explains the matching flow but not irreversibility, safety expectations, or permissions, leaving an agent with an incomplete risk picture.

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 100%, so the baseline is 3. The description adds real meaning beyond the schema: id triggers a direct delete, while query uses keyword matching with confident-match deletion or candidate listing. That clarifies how the optional parameters select behavior.

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 names a specific verb and resource (delete a memory) and clearly distinguishes two operating modes: direct deletion by id versus query-based lookup. It does not explicitly compare itself with sibling tools, but the purpose is unambiguous.

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?

It states the target scenario clearly: stale or wrong memories. It also explains the two modes and when each is appropriate, though it does not explicitly warn when not to use this tool or name an alternative.

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