Skip to main content
Glama
Skitchy

Rekindle

by Skitchy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

delete_memory

Permanently deletes a single memory by ID from the local SQLite database, removing its full-text search entry. Use it to clear outdated, incorrect, or irrelevant memories; deletion is irreversible.

Instructions

Permanently delete a single memory from the local SQLite database by its ID. This action is irreversible — the row and its full-text search index entry are removed immediately. Use when a memory is outdated, incorrect, or no longer relevant. Returns {success: true} if the memory was found and deleted, or {success: false, message: 'Memory not found'} if the ID does not exist. Does not affect other memories or session records.

Input Schema

NameRequiredDescriptionDefault
idYesThe UUID of the memory to delete. Obtain from store_memory, search_memory, or list_memories results.
provenanceNoWrite attribution. Required when REKINDLE_REQUIRE_WRITE_PROVENANCE=1; never proof of authorization.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / provenance
      Added value: +{
+  "description": "Write attribution. Required when REKINDLE_REQUIRE_WRITE_PROVENANCE=1; never proof of authorization.",
+  "properties": {
+    "author_identity": {
+      "description": "Claimed writer identity; attribution, not authentication.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "authorization_reference": {
+      "description": "Caller-supplied authority reference. Stored as unverified and never treated as authorization.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "client": {
+      "description": "Client performing the write, for attribution only.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "request_id": {
+      "description": "Unique caller request identifier.",
+      "minLength": 1,
+      "type": "string"
+    },
+    "thread_id": {
+      "description": "Calling thread or session identifier.",
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "client",
+    "thread_id",
+    "request_id",
+    "author_identity",
+    "authorization_reference"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv0.3.0
    • changedInput schema / properties / id / description
      Previous value: -"The memory ID to delete"New value: +"The UUID of the memory to delete. Obtain from store_memory, search_memory, or list_memories results."
  3. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does most of it well: it declares irreversibility, that the FTS index entry is removed immediately, the blast radius (other memories and session records unaffected), and both success/failure return shapes. The one gap is the conditional write-provenance requirement, which is a real behavioral precondition disclosed only in the schema, not here.

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 action and its irreversibility in the first two sentences, then usage, then return contract. Four sentences with essentially no padding; the 'Does not affect other memories or session records' line is the only one bordering on redundant given the singular-object framing.

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 destructive single-record deletion with no output schema, the description covers effect, reversibility, scope, trigger condition, and both return values — enough for an agent to call it safely. The only unaddressed element, provenance gating, is fully documented in the required schema field.

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%, including where to obtain the UUID and the full provenance contract, so the schema already does the heavy lifting. The description only adds the framing 'by its ID' and does not mention provenance at all, which is acceptable at the baseline but adds no surplus meaning.

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 ('Permanently delete a single memory') plus the mechanism ('from the local SQLite database by its ID'), which cleanly distinguishes it from update_memory, store_memory, and search_memory. No ambiguity about what the tool does.

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 a clear trigger condition ('Use when a memory is outdated, incorrect, or no longer relevant') and a negative scope ('Does not affect other memories or session records'). It does not name an alternative for the common case of a memory being wrong rather than obsolete — e.g., pointing to update_memory when correction is preferable to deletion — so it stops short of full routing guidance.

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