Skip to main content
Glama

Forget XMemo memory or TODO

forget
Destructive

Delete one memory, TODO, or Ledger transaction by current/latest, an exact memory reference, an exact TODO ID from list_memory_todos, or an exact Ledger transaction ID. The default is a recoverable soft delete that restore_memory can undo; mode='hard' is permanent and unrecoverable; requires explicit user confirmation of permanent deletion. Ambiguous targets are resolved before deleting.

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
modeNoDeletion mode: soft or soft_delete is the recoverable default; hard or hard_delete is permanent and unrecoverable; requires explicit user confirmation of permanent deletion.soft
reasonNoOptional user-facing reason for the deletion.
targetNoThe memory to forget: current or an exact memory ID shown by search.current
memory_idNoExact XMemo memory reference shown by search or recall.
query_hintNoInput value for the Forget tool.
metadata_jsonNoOptional JSON object string with extra metadata for the operation.{}
replacement_contentNoReplacement text to store when redacting or replacing deleted memory content.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"Deletion mode: soft or soft_delete is the recoverable default; hard or hard_delete is permanent and unrecoverable and may be used only after explicit user confirmation."New value: +"Deletion mode: soft or soft_delete is the recoverable default; hard or hard_delete is permanent and unrecoverable; requires explicit user confirmation of permanent deletion."
  2. Changed4 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / metadata_json
      Added value: +{
      +  "default": "{}",
      +  "description": "Optional JSON object string with extra metadata for the operation.",
      +  "title": "Metadata Json",
      +  "type": "string"
      +}
    • addedInput schema / properties / query_hint
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Input value for the Forget tool.",
      +  "title": "Query Hint"
      +}
    • addedInput schema / properties / replacement_content
      Added value: +{
      +  "default": "",
      +  "description": "Replacement text to store when redacting or replacing deleted memory content.",
      +  "title": "Replacement Content",
      +  "type": "string"
      +}
  3. Changed8 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / memory_id
      Added value: +{
      +  "default": "",
      +  "description": "Exact XMemo memory reference shown by search or recall.",
      +  "title": "Memory Id",
      +  "type": "string"
      +}
    • removedInput schema / properties / metadata_json
      Removed value: -{
      -  "default": "{}",
      -  "description": "Optional JSON object string with extra metadata for the operation.",
      -  "title": "Metadata Json",
      -  "type": "string"
      -}
    • changedInput schema / properties / mode / default
      Previous value: -"hard"New value: +"soft"
    • changedInput schema / properties / mode / description
      Previous value: -"Deletion mode for forget_memory, such as soft_delete, hard_delete, or redact when supported."New value: +"Deletion mode: soft or soft_delete is the recoverable default; hard or hard_delete is permanent and unrecoverable and may be used only after explicit user confirmation."
    • addedInput schema / properties / mode / enum
      Added value: +[
      +  "soft",
      +  "soft_delete",
      +  "hard",
      +  "hard_delete"
      +]
    • removedInput schema / properties / query_hint
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "Input value for the Forget tool.",
      -  "title": "Query Hint"
      -}
    • removedInput schema / properties / replacement_content
      Removed value: -{
      -  "default": "",
      -  "description": "Replacement text to store when redacting or replacing deleted memory content.",
      -  "title": "Replacement Content",
      -  "type": "string"
      -}
  4. Changed1 schema field changed
    • changedInput schema / properties / mode / default
      Previous value: -"soft"New value: +"hard"
  5. Changed4 schema fields changed
    • addedInput schema / properties / metadata_json
      Added value: +{
      +  "default": "{}",
      +  "description": "Optional JSON object string with extra metadata for the operation.",
      +  "title": "Metadata Json",
      +  "type": "string"
      +}
    • addedInput schema / properties / mode
      Added value: +{
      +  "default": "soft",
      +  "description": "Deletion mode for forget_memory, such as soft_delete, hard_delete, or redact when supported.",
      +  "title": "Mode",
      +  "type": "string"
      +}
    • addedInput schema / properties / query_hint
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Input value for the Forget tool.",
      +  "title": "Query Hint"
      +}
    • addedInput schema / properties / replacement_content
      Added value: +{
      +  "default": "",
      +  "description": "Replacement text to store when redacting or replacing deleted memory content.",
      +  "title": "Replacement Content",
      +  "type": "string"
      +}
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

It goes well beyond destructiveHint=true. It explains that soft deletes are recoverable through restore_memory, hard deletes are permanent, permanent deletion needs user confirmation, and ambiguous targets are resolved before deleting. It does not explain how ambiguity is resolved, for example whether the tool prompts or picks one. Nothing contradicts the annotations.

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?

Three dense sentences, front-loaded with the action and targets. The second sentence is awkwardly punctuated, with chained semicolons, but there is no real waste.

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?

An output schema exists, and the safety semantics are well covered. Gaps remain for a 7-parameter destructive tool: the target/memory_id overlap, how Ledger IDs are passed, and the purpose of query_hint and replacement_content.

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 nominally 100%, but query_hint has a meaningless description and replacement_content's redaction role is not explained. The description does not clarify how target and memory_id relate, or how a TODO or Ledger ID should be supplied when target's schema mentions only memory IDs. It adds the list of target forms, which helps somewhat.

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?

It names a specific action (delete) and three resource types: memory, TODO, and Ledger transaction. It lists the accepted target forms and points to the sibling list_memory_todos for TODO IDs. This separates it from complete_memory_todo and update_memory.

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 says hard mode requires explicit user confirmation and that restore_memory undoes soft deletes. It points to list_memory_todos for IDs. It does not say when to prefer complete_memory_todo, or when to use update_memory or redaction via replacement_content instead of deletion.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.