Skip to main content
Glama

remember

Save durable memories with automatic deduplication: re-remembering a fact updates it instead of creating duplicates, keeping notes refined across sessions.

Instructions

Save a durable memory. UPSERTS: a memory of the same type with the same (whitespace/case-normalized) title is updated in place instead of duplicated, so re-remembering a fact refines it rather than cluttering.

Worth remembering: decisions and their reasons, conventions, gotchas that cost time, the user's preferences and how they like to work, facts about the environment (paths, commands, accounts) you had to discover. Not worth it: anything derivable from the code, or a transcript of what you did. Remember it when you learn it, not at the end of the session.

Memories of type project/feedback/reference are tagged with the current project automatically (proj:<name>, from CLAUDE_PROJECT_DIR) unless you pass a proj: tag yourself; user memories are about the person and stay global.

Args: type: one of "user", "feedback", "project", "reference". title: a short label; also the dedup key within a type. body: the fact. For feedback/project, a "Why:" / "How to apply:" line helps. tags: optional comma-separated tags. links: optional list of related memory ids. Merged (union) into any links already on the memory, never replaces them - omitting this on a refine call preserves links set earlier. crystallizes: optional list of source memory ids this memory abstracts; links it over them as a crystallized principle (needs TETHER_CRYSTALLIZE).

Returns {"id", "action"} where action is "created", "updated", or (with TETHER_CONSOLIDATE on) "consolidated" - a near-duplicate was superseded.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYes
tagsNo
typeYes
linksNo
titleYes
crystallizesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.0

TDQS

A4.8/5.0
Behavior4/5

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

No annotations provided, so description carries the burden. It discloses created/updated/consolidated outcomes, link merge behavior, crystallize requirements, and auto-tagging. Does not explicitly mention persistence side effects, but 'durable memory' implies it. Strong transparency overall.

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?

Long but well-organized with clear sections: purpose, guidance, tagging, parameter list, return. Each sentence provides distinct value; no fluff or redundancy. Front-loaded with core proposition.

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?

Covers all operational aspects: return value shape, action outcomes, conditional flags, auto-tagging, link merging, and dedup behavior. Sufficient for an agent to invoke correctly without external context.

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

Parameters5/5

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

Schema coverage is 0%, but the description fully compensates: explains type enum values, title as dedup key, body with formatting advice, tags format, links merge semantics, and crystallizes condition. Every parameter is covered with usage context.

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 ('Save') and resource ('durable memory') with explicit upsert semantics. Clearly differentiates from siblings recall/link/forget as the write operation.

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

Usage Guidelines5/5

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

Provides explicit 'Worth remembering' vs 'Not worth it' guidance, advises when to use (learn it when you learn it) and when not (derivable from code). Also explains automatic tagging and flag-dependent behaviors.

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