Skip to main content
Glama
Master0fFate

LatentContext MCP Server

by Master0fFate

memory_forget

Remove, correct, or deprecate stored memories to keep information accurate and up-to-date. Use this tool when facts change or need cleanup.

Instructions

Mark a memory as outdated, incorrect, or to be deleted.

WHEN TO USE:

  • When the user corrects previously stored information.

  • When stored facts become outdated (e.g., user changed jobs, moved cities).

  • When duplicate or incorrect memories need cleanup.

ACTIONS:

  • 'deprecate': Lowers confidence score so the memory is deprioritized but not removed. Use when unsure.

  • 'correct': Replaces the memory content with new, correct information. Requires the 'correction' parameter.

  • 'delete': Permanently removes the memory. Use for clearly wrong or duplicate entries.

You need the memory_id which is returned when you store a memory, or visible in memory_status output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
memory_idYesID of the memory to modify (UUID format, returned by memory_store).
actionYesAction to take: 'deprecate' (lower priority), 'correct' (replace content), 'delete' (remove permanently).
correctionNoNew content to replace the memory with. Required when action is 'correct'.
Behavior5/5

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

No annotations provided, so the description fully explains behavioral traits: effects of each action (deprecate, correct, delete), prerequisites (memory_id), and conditional parameter requirements.

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 well-organized with sections, bullet points, and clear headings. Every sentence is informative and concise, no 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?

For a modification tool with 3 parameters, conditional logic, and no output schema, the description is comprehensive. It could mention return values or effects on other operations, but current level is sufficient.

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 coverage is 100%, baseline 3. The description adds value by explaining the action enum meanings and clarifying the conditional requirement for 'correction' parameter when action='correct'.

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 clearly states the tool's purpose: 'Mark a memory as outdated, incorrect, or to be deleted.' It distinguishes from siblings (memory_store, memory_retrieve) by focusing on modification/removal.

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?

Provides explicit 'WHEN TO USE' bullets covering common scenarios. Lacks explicit when NOT to use, but the context is clear. Siblings are listed externally.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Master0fFate/LatentContext-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server