Skip to main content
Glama
Sign In
memory-lite-mcp

memory-lite-mcp

by jipbapkitchen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

forget

Destructive

Delete a stored memory by its ID to remove obsolete or unwanted entries from the local SQLite-backed memory store.

Instructions

Delete a memory by id.

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 observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

The primary behavioral trait of this tool is that it is destructive, which is explicitly covered by the annotation `destructiveHint: true`. The description simply restates the action ('Delete'), adding minimal novel behavioral context beyond what the structured data provides.

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?

The description is perfectly sized: a single, direct sentence that contains all necessary actionable information without any fluff.

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?

Given the simplicity of the single-parameter schema, the description is adequate for an agent to understand and execute the tool. There are no obvious gaps in functionality or constraints that aren't already defined by the `destructiveHint` annotation.

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?

With only one parameter and 0% schema coverage, the description relies heavily on the name 'id' to communicate that it matches the input schema. It provides no additional semantic value beyond naming the parameter's role.

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 description is extremely clear, using the specific verb 'Delete' on the resource 'memory' using the specific identifier 'id'. This immediately distinguishes it from the retrieval ('recall') and creation ('remember') siblings.

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

Usage Guidelines3/5

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

While it defines the required method (by ID), it does not provide guidance on when to use it (e.g., 'when memory is no longer relevant') versus just stating its function. Its guidance is implied by the destructive action, but lacks specific context.

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