JauMemory MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

forget

Delete a specific memory record using its unique ID. Helps maintain accurate and relevant memory storage by removing outdated or incorrect entries.

Instructions

Delete a specific memory

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

Input Schema

Name	Required	Description	Default
`memoryId`	Yes	Memory ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.3May 31, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Delete', which is inherent from the tool name 'forget'. It does not reveal whether the deletion is permanent, requires authorization, or has cascading effects on related data.

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 a single sentence with zero wasted words. It is front-loaded and appropriately sized for a simple delete operation.

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 tool with one parameter, no output schema, and a straightforward purpose, the description is minimally adequate. However, it could be improved by clarifying what constitutes a 'memory' in this context (e.g., vs. 'collection' siblings) and noting any return value or side effects.

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?

The input schema has 100% coverage and already describes the single parameter 'memoryId' as 'Memory ID to delete'. The description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate as per criteria.

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 'Delete a specific memory' uses a clear verb ('Delete') and resource ('a specific memory'), directly conveying the tool's action. It distinguishes from siblings like 'remember' (store), 'recall' (retrieve), 'analyze', 'consolidate', and 'delete_collection' (which targets collections, not memories).

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives such as 'update' (to modify a memory) or 'delete_collection'. There is no mention of prerequisites, exclusions, or context for invoking 'forget' over other memory-related tools.

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