Skip to main content
Glama
Sign In
Memory Nexus MCP

Memory Nexus MCP

by KairosMobius
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

forget

Delete a specific memory by ID from Memory Nexus. Optionally cascade to remove connected memories, helping maintain a clean knowledge base.

Instructions

Remove a memory. Use sparingly.

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
cascadeNoAlso remove connected memories
memory_idYesMemory ID to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are present, so the description carries full burden. It implies destructiveness via 'Remove' and 'Use sparingly,' but doesn't disclose irreversibility, cascade side effects, or permissions. This is inadequate for a destructive tool.

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 short sentences with no waste. 'Remove a memory' is front-loaded, and 'Use sparingly' contributes a warning. It is appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has moderate complexity with a destructive action, no output schema, and no annotations. The description only states the basic removal and a vague warning, omitting essential details like cascade behavior, reversibility, or return values. This is under-specified.

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 descriptions cover both parameters (memory_id and cascade) at 100%, so the baseline is 3. The description adds no additional parameter semantics beyond what the schema already provides.

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 says 'Remove a memory' – a specific verb and resource. It clearly distinguishes from sibling tools like remember (add) and 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 Guidelines2/5

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

The only usage guidance is 'Use sparingly,' which is a vague caution rather than an explanation of when to use this tool or when to prefer alternatives. No prerequisites or exclusions are mentioned.

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