Skip to main content
Glama
Sign In
Ragionex Memory MCP

Ragionex Memory MCP

Official
by ragionex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Delete memories

ragionex_delete_memory
DestructiveIdempotent

Moves specified memory record IDs to trash in the selected Vault for records that are wrong, repeated, or no longer needed; restorable for 30 days.

Instructions

Move the specified record IDs to trash in the selected Vault. Requires delete permission. Use it for records that are wrong, repeated or no longer true, and for records the user asks to remove. Records can be restored for 30 days. Returns the number moved; it does not delete or select a Vault. Permanent deletion is available only in the dashboard.

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": {
      "ids": "<ids>"
    },
    "name": "ragionex_delete_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesRecord IDs to move to trash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • changedInput schema / properties / ids / description
      Previous value: -"Memory IDs to delete."New value: +"Record IDs to move to trash."
    • addedInput schema / properties / ids / items / pattern
      Added value: +"^[A-Za-z0-9_]{1,14}$"
  2. First observedv0.5.1

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the destructive/idempotent annotations, it discloses the soft-delete model, a 30-day restorability window, a delete-permission requirement, the return value ('number moved'), and that it neither deletes permanently nor selects a Vault. This is exactly the extra context annotations cannot convey.

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 action and target come first, followed by prerequisites, use cases, reversibility, and return value in short declarative sentences. No sentence is filler and nothing important is buried at the end.

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?

Even without an output schema, the description says it returns the number moved, and it covers permission requirements, reversibility, and the Vault caveat. An agent has everything needed to call it safely without opening the schema.

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% for the single ids parameter, so the baseline is already high. The description adds that multiple IDs are moved as a batch and that Vault selection is not a parameter of this tool, which clarifies scope beyond the raw schema.

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?

States a specific verb and resource: 'Move the specified record IDs to trash in the selected Vault.' It also draws the boundary against permanent deletion ('it does not delete') and against Vault selection, which distinguishes it from siblings like ragionex_restore_memory and ragionex_list_trash.

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 concrete use criteria: 'records that are wrong, repeated or no longer true, and for records the user asks to remove,' and implicitly excludes permanent deletion by naming the dashboard as the only route for it. It stops short of naming sibling tools as alternatives, but the when/when-not split is clear.

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