Skip to main content
Glama
Sign In
Unified Memory MCP

Unified Memory MCP

by yksanjo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Forget Memory

forget_memory
Destructive

Permanently delete a specific memory entry from the local vault by providing its ID and optional reason.

Instructions

Hard-delete a memory entry from the local vault.

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_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior3/5

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

The description adds 'Hard-delete' complementing the destructiveHint=true annotation by clarifying irreversibility. However, it does not disclose other behavioral traits like permission requirements or cascade effects, so it provides moderate value beyond annotations.

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?

The description is a single sentence with no wasted words. It is front-loaded and efficient, though it could benefit from additional detail without becoming verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 0% schema description coverage, no output schema, and two parameters, the description is insufficient. It omits explanations for parameters (especially 'reason') and return behavior, leaving significant gaps for an agent to use the tool correctly.

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

Parameters1/5

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

Schema description coverage is 0%, and the description does not explain the purpose of the 'reason' parameter or provide any guidance on parameter usage. The description adds no meaning beyond the schema's raw property definitions.

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 'Hard-delete a memory entry from the local vault.' clearly states the action (hard-delete), the resource (memory entry), and the scope (local vault), making it specific and distinguishable from siblings like update_memory or search_memory.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives. The description does not mention when to prefer this over update_memory (soft delete) or other tools, leaving the agent without context for selection.

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