Skip to main content
Glama
Sign In
engram-mcp

engram-mcp

by Cartisien
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

forget

Delete session memories by removing all entries, a specific memory by ID, or entries before a given date.

Instructions

Delete session memories. Delete all, one by ID, or entries before a date.

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

Input Schema

NameRequiredDescriptionDefault
sessionIdYesSession identifier
idNoSpecific memory ID to delete (optional)
beforeNoISO date — delete entries before this date (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It indicates a destructive operation but lacks details on reversibility, authorization needs, rate limits, or side effects. The phrase 'Delete all' is alarmingly vague.

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?

The description is extremely concise, consisting of two sentences with no redundant words. It is front-loaded with the core action and immediately outlines the three deletion modes.

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 deletion tool with three optional modes, the description covers the main use cases. However, it omits return value (e.g., success/failure indication) and does not explain the required sessionId context. Given no output schema, more detail on results would be helpful.

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% with each parameter described. The description adds semantic value by grouping modes (all, by ID, before date) that map to parameters, providing context beyond individual parameter descriptions.

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 clearly states the action 'Delete session memories' and specifies three distinct modes: delete all, one by ID, or entries before a date. This distinguishes it from sibling tools like 'remember' (add) or 'recall' (retrieve).

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?

The description implies usage for deletion but does not explicitly state when to use this tool versus alternatives like 'forget_user'. No exclusions or when-not-to-use guidance is provided.

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