Skip to main content
Glama
jagoff

MEMO MCP Server

by jagoff

memo_forget

Destructive

Hide a memory from recall and search while preserving its history. Optionally record why for future restoration.

Instructions

Mark one memory as forgotten without deleting its history.

Destructive in retrieval behavior: the memory is hidden from normal recall/search surfaces until memo_unforget restores it. Pass reason to record why the memory should no longer be surfaced.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId or unique prefix of the memory to hide from recall.
reasonNoOptional free-text reason recorded in the memory's metadata as forget_reason.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Annotations provide destructiveHint=true, and description elaborates: hidden from recall/search until memo_unforget restores it. Reversible nature clearly stated. No contradictions with annotations.

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?

Three concise sentences, front-loaded with main purpose, no wasted words. Efficiently conveys all necessary information.

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?

With output schema present and low complexity (2 simple params), the description covers all needed aspects: purpose, effect, parameter roles, and relationship to sibling tools.

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%, but description adds value: for 'id' mentions 'unique prefix' not in schema; for 'reason' explains purpose. Adds meaningful context beyond schema.

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?

Description clearly states 'Mark one memory as forgotten without deleting its history.' It uses a specific verb (mark) and resource (memory), and distinguishes from siblings like memo_delete and memo_unforget.

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?

Explanation of destructive retrieval behavior and mention of memo_unforget for restoration provides context. Could explicitly state when to use memo_delete instead, but the guidance is clear enough.

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/jagoff/memo'

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