Maindex Smart Memory Service

This connector has been deprecated

Replaced by Maindex Smart Memory Service.

Duplicate entry

forget

DestructiveIdempotent

Soft-delete a memory by mem-* ID, or with wipe_history=true permanently purge all revisions (IRREVERSIBLE). When wipe_history is true, confirm_irreversible_wipe must also be true or a confirmation prompt is returned. Soft-delete (default) is safe and reversible.

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

Input Schema

Name	Required	Description
`target_id`	Yes	Memory ID (mem-xxxx or team-slug:mem-xxxx).
`wipe_history`	No	If true, permanently purge all revisions and blank the body (IRREVERSIBLE). Otherwise soft-delete only. When true, confirm_irreversible_wipe must also be true or a confirmation prompt is returned instead.
`confirm_irreversible_wipe`	No	Required confirmation when wipe_history is true. Must be explicitly set to true to authorize irreversible permanent purge of all revisions. If wipe_history is true and this field is missing or false, the tool returns a confirmation prompt instead of executing the destructive action.

Output Schema

Name	Required	Description
`wiped`	No	Whether revision history was permanently purged
`deleted`	Yes	Whether the memory was deleted
`success`	Yes	Whether the operation succeeded
`traceId`	Yes	Trace ID for debugging

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations declare destructiveHint=true, but the description adds the crucial nuance they cannot: the default path is reversible, the destructive path purges all revisions permanently, and a missing confirmation flag yields a prompt rather than execution. That is real behavioral value beyond the structured metadata.

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?

Front-loaded with the two modes and the IRREVERSIBLE warning in caps. The closing sentence ('Soft-delete (default) is safe and reversible') partly repeats the first sentence, a small redundancy in an otherwise tight three-sentence definition.

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

Completeness5/5

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

For a 3-parameter mutation tool with full schema coverage, annotations, and an output schema, this covers the essential gaps: which mode is safe, which is permanent, and the confirmation gate. Nothing an agent needs in order to call it correctly is missing.

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 100% and output_schema exists, so the schema already documents target_id, wipe_history, and confirm_irreversible_wipe in detail. The description restates the coupling and consequences of those flags, which reinforces but does not add new meaning beyond the structured fields.

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?

Names two specific verbs (soft-delete vs permanently purge) on a single resource (a memory identified by mem-* ID), and draws the default/irreversible distinction up front. An agent can immediately tell this apart from keep, recall, or update.

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?

Gives clear mode-selection guidance: default is the safe reversible path, wipe_history=true is the destructive path requiring confirmation. It does not explicitly route against siblings (e.g., use update to change content, forget to remove), so it falls short of full when/when-not/alternatives coverage.

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

All Maindex Smart Memory Service tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?