Skip to main content
Glama
sassyconsultingllc

SassyMCP

Official
by sassyconsultingllc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sassy_memory_forget

Destructive

Permanently deletes a specific memory record by its exact key, with no undo or recovery. Use to remove obsolete or incorrect stored information that should not persist, while ensuring precise, irreversible deletion.

Instructions

Mutating and destructive: permanently deletes the single memory record whose key exactly matches. key (required) must match exactly — only that one record is removed, and there is no undo, trash, or recovery. Returns {"forgotten": true|false, "key", "error"}; forgotten is false with an error message if no record matches. Use only when stored information is obsolete, wrong, or should not persist across sessions. Milestones written by sassy_memory_log live in a separate append-only table and cannot be deleted by this tool. Never use to clear state at session end — that is what sassy_memory_handoff is for.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYes
errorYes
forgottenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.15.1
    • addedOutput schema / properties / error
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "title": "Error"
+}
    • addedOutput schema / properties / forgotten
      Added value: +{
+  "title": "Forgotten",
+  "type": "boolean"
+}
    • addedOutput schema / properties / key
      Added value: +{
+  "title": "Key",
+  "type": "string"
+}
    • removedOutput schema / properties / result
      Removed value: -{
-  "title": "Result",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "result"
-]New value: +[
+  "forgotten",
+  "key",
+  "error"
+]
    • changedOutput schema / title
      Previous value: -"sassy_memory_forgetOutput"New value: +"ForgetResult"
  2. First observedv0.1.0

TDQS

A5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description layers on substantial additional context: irreversibility ('no undo, trash, or recovery'), exact-match semantics, the forgotten:false error path when no record matches, and the exclusion of sassy_memory_log milestones. All statements are consistent with the annotations.

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?

Six sentences, each carrying a distinct fact: core action, match/irreversibility, return contract, usage condition, milestone exclusion, and handoff routing. It is front-loaded with the destructive action and contains zero filler.

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 one-parameter destructive delete with annotations and an output schema, nothing an agent needs to invoke it correctly is missing: purpose, safety profile, return semantics, exclusion of milestones, and the routing alternative are all present. No open questions remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden. It explains the single parameter meaningfully: 'key (required) must match exactly — only that one record is removed,' plus the no-match error behavior. The '(required)' hint slightly duplicates the schema's required array, but the exact-match and single-record semantics are genuine added value.

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 deletes the single memory record whose key exactly matches' — with precise single-record scope. This differentiates it from siblings like sassy_memory_search, sassy_memory_remember, and sassy_memory_log without opening any of their schemas.

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?

Gives an explicit when-to-use condition ('Use only when stored information is obsolete, wrong, or should not persist across sessions') and an explicit when-not-to-use with a named alternative ('Never use to clear state at session end — that is what sassy_memory_handoff is for'). Nothing is left 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