Skip to main content
Glama

Configure Memory

configure_profile_forget

Destructive

Delete the user's memories that YOU saved or imported. WHICH to delete: if you hold an id, pass id ("mem_..."); if you do NOT have an id and the user names a topic, pass match with a word the memory contains (match: "nursing") and forget finds and deletes your matching memories itself, no search first. HOW: pass reason "user_request" whenever the user wants it gone for good or says never mention it again (this suppresses the content from re-saving and re-importing); use the default correction only for fixing your own mistake. A match previews first: it returns a count and the matching memories and deletes NOTHING until you call again with confirm: true, so review and confirm only what the user meant. import_id (from configure_profile_import) retracts one whole import; scope ("imports", "saved", "all") clears everything of yours at once. Pass exactly one selector. Reach is your own writes only: never another agent's memories, never an import the user ran themselves, never the profile's settled facts, and this deletes memories only, never the Configure account. An id outside your reach returns a clean not-found, not an error. Deletion is permanent for your copy. Returns the deleted memory id and which source it lived under.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoOne memory to delete, by the id returned when it was saved (format "mem_...", also shown on entries in your own source box). Use exactly one selector: id, import_id, or scope.
dateNoOptional. The memory's date ("YYYY-MM-DD") if known, from the saved path or entry; providing it makes the delete a direct lookup instead of a namespace scan.
matchNoSelector. Words a memory contains, e.g. "nursing" or "coffee". Finds YOUR OWN matching memories and deletes them, so you do not need a separate search to get ids first. A match WITHOUT confirm:true returns a count and preview and deletes nothing; call again with confirm:true to delete. Reach for this the moment a user says "delete the X stuff" and you do not already hold ids.
scopeNoDelete everything of yours in one call, instead of one id at a time. "imports": every memory you brought in through configure_profile_import, including older imports that predate import ids. "saved": everything you saved with remember or commit. "all": both. Only your own writes are ever touched, so this can never reach another assistant's memories or the profile's settled facts.
reasonNoOptional, default "correction". Use "user_request" ONLY when the user explicitly asked you to remove this and not bring it back (for example "delete that" or "never call me that again") — it additionally suppresses the same content from every source and blocks it from being re-saved or re-imported. Use "correction" (or omit) when you are fixing your own mistake or retracting something stale.
confirmNoOnly with match. Omit or false to preview (count + the memories that match, deletes nothing). Set true to delete the matched memories. Preview first unless the user was unambiguous.
import_idNoOptional, and used instead of id. The import_id returned by configure_profile_import: retracts every memory that import created, in one call, instead of one delete per memory. Only entries from an import you performed are touched.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe id of the deleted memory — the confirmation the caller acts on.
errorNoPresent when the id was malformed or not found in your namespace.
matchNoThe match words this call used, echoed back.
deletedYesWhether anything was removed by this call. False on previews and no-matches.
matchedNoFor match-based forgets: how many memories matched.
messageNo
previewNoMemories a match would delete; nothing is deleted until confirm is true.
deleted_idsNoIds of the memories a confirmed match deleted.
deleted_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, readOnlyHint=false and idempotentHint=false, but the description goes well beyond them: reach is limited to your own writes (never another agent's memories, a user-run import, or settled profile facts), match deletes nothing until confirm:true, user_request suppresses re-saving/re-importing, and an out-of-reach id returns a clean not-found rather than an error. These are material behavioral facts not encoded in structured fields.

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?

It is front-loaded with the purpose and then organized around WHICH/HOW selectors, so structure is strong and most sentences carry operative detail. It is dense and longer than strictly needed (some selector semantics repeat what the schema states), keeping it just below the top score.

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, seven-parameter tool with an output schema present, the description covers the risky decision points — reach, preview/confirm, suppression, selector exclusivity — without redundantly explaining return values. An agent has everything needed to invoke it safely and correctly.

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 description coverage is 100%, so the schema already documents each parameter, giving a baseline of 3. The description adds genuine extra meaning — the one-selector exclusivity rule, the confirm-gated preview semantics of match, the re-save suppression of user_request, and the reach boundary on import_id — so it exceeds the baseline rather than merely restating it.

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?

The opening sentence states a specific verb (Delete) and a precisely scoped resource (the user's memories that YOU saved or imported), immediately bounding reach. This cleanly separates it from siblings like configure_profile_remember, configure_profile_import, and configure_profile_search without needing 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?

It gives explicit selection logic: use id when you hold one, match when the user names a topic, import_id to retract a whole import, scope to clear everything at once, and 'pass exactly one selector'. It also states when to use reason 'user_request' vs 'correction', and that a match must be previewed and confirmed — the full when/when-not decision tree is present.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources