Skip to main content
Glama
Sign In
Rememb

Rememb

by LuizEduPP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rememb_delete

Soft-delete one or more memory entries by ID to hide them from reads and search while keeping them restorable later.

Instructions

Soft-delete one memory entry by its ID or multiple entries via entry_ids[]. Deleted entries are hidden by default from reads and search, but can be restored later. Use rememb_restore to undo a deletion. Use rememb_clear to permanently delete all entries at once.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "rememb_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNoMemory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.global
entry_idNoEntry ID to delete
entry_idsNoBatch deletion IDs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.20
    • addedInput schema / properties / entry_ids
      Added value: +{
+  "description": "Batch deletion IDs.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / store
      Added value: +{
+  "default": "global",
+  "description": "Memory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.",
+  "enum": [
+    "global"
+  ],
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "entry_id"
-]
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does well: it discloses that deletion is soft, that entries are hidden from reads/search by default, and that they remain restorable. It stops short of stating behavior for unknown IDs, partial batch failures, or idempotency of repeat deletes.

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?

Three short sentences, front-loaded with the operation and its two modes, then the soft-delete consequence, then the sibling routing. Every sentence adds information; nothing is redundant.

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

Completeness4/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 no annotations and no output schema, the description covers the essential semantics: soft vs permanent, visibility impact, and restore path. Edge-case behavior (nonexistent ID, mixed batch results, whether entry_id and entry_ids can be combined) is left unaddressed.

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 description coverage is 100%, so entry_id, entry_ids, and store are already documented in the schema. The description only restates the two deletion paths and adds no format, limits, or precedence rules for entry_id vs entry_ids — baseline 3 applies.

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 ('Soft-delete') and resource ('memory entry'), and covers both single (entry_id) and batch (entry_ids[]) modes in the first sentence. It is clearly distinguishable from rememb_restore and rememb_clear, which it names explicitly.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use rememb_restore to undo, use rememb_clear for permanent bulk deletion. That gives both the undo path and the alternative for the destructive-bulk case, leaving little to inference.

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