Skip to main content
Glama
Sign In
agent-memory-sqlite

agent-memory-sqlite

by Urthella
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

forget

Destructive

Delete a stored memory by its numeric ID, such as the #number shown by recall or recent, to remove outdated or incorrect facts from the SQLite memory store.

Instructions

Delete a memory by its id (the #number shown by recall and recent).

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": {
      "id": "<id>"
    },
    "name": "forget"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, and 'Delete' is consistent with that. The description adds that the id is a displayed #number, which is genuinely useful context, but it does not say whether deletion is permanent or recoverable, which matters for a destructive operation.

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?

One short sentence with zero waste; the action and the parameter clarification are both front-loaded with no filler.

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 one-parameter destructive tool with no output schema, this covers what an agent needs to call it correctly, with the only gap being the irreversibility/return behavior after deletion.

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?

The schema coverage is 0% and the single integer parameter is undocumented in the schema, so the description carries the burden. It explains that the id is the '#number shown by recall and recent', giving the agent the syntactic form and provenance of the value rather than just 'an integer'.

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 (delete) and resource (a memory) and immediately clarifies the identifier's origin by naming the sibling tools recall and recent. This distinguishes it cleanly from its siblings, which only read or create memories.

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?

Implies the workflow: use recall or recent first to obtain the #number, then call forget with it. There is no explicit when-not guidance or warning about alternatives, but the context of use 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