Skip to main content
Glama

remember

Save durable knowledge—decisions, gotchas, procedures, and observations—so it survives context compaction and can be recalled later.

Instructions

Use remember when you learn something durable — a decision, a gotcha, a non-obvious fact, a procedure — so it survives context compaction.

remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference.

Call it at these five moments, not at the end and not never: a non-obvious root cause or gotcha (fact); a ratified design decision with its reason (fact); a repeatable how-to (procedure); a judgement you will revisit (opinion); and once before submitting a mission result (observation). Always pass your own agent_handle — the daemon cannot infer it, and a subagent's working directory resolves to the repo's leader, not to you.

The daemon scrubs secrets/PII before indexing. Returns immediately — the daemon indexes in the background.

Args: content: The text content to remember. document_name: Name for the document (e.g., 'notes.md'). overwrite: If true, replace existing data for this document. If false, an existing document of this name is left untouched. collection: Collection name. Leave empty to route by agent_handle — memory-<handle> when a handle is given, else default. format_hint: Format hint: 'auto', 'plain', 'markdown', 'latex'. agent_handle: Your own handle (e.g. "rmh") — the memory is filed under it and recalled by it. memory_type: Memory classification: fact, observation, opinion, procedure. 'lesson' is reserved for the learn tool. summary: One-line summary of the content.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes
summaryNo
overwriteNo
collectionNo
format_hintNoauto
memory_typeNo
agent_handleNo
document_nameYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.2.0
    • changedInput schema / properties / collection / default
      Previous value: -"default"New value: +""
  2. First observedv2.1.0

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well by disclosing that the daemon scrubs secrets/PII, that it returns immediately while indexing happens in the background, and that agent_handle must be passed explicitly because the daemon cannot infer it. It could go further by noting failure modes or eventual consistency, but the key behavioral traits are covered.

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 long but well-organized: front-loaded usage context, then behavior notes, then parameter explanations. Some phrases are slightly conversational, but no major redundancy exists given the need to document 8 parameters with no schema descriptions.

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?

For an 8-parameter tool with no annotations and no schema descriptions, this description covers usage timing, sibling distinctions, parameter semantics, background behavior, privacy handling, and the subagent agent_handle gotcha. It is effectively complete for an agent to select and invoke the tool correctly.

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 description coverage is 0%, so the description must compensate — and it does. Every parameter receives a meaningful explanation, including default routing behavior for collection, the reserved 'lesson' value for memory_type, and overwrite semantics. This exceeds what the bare schema provides.

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 states a specific verb and resource: 'use remember when you learn something durable.' It explicitly distinguishes itself from sibling tools by saying 'remember = a specific durable fact, ingest = a URL, learn = a distilled lesson that gets retrieval preference,' so an agent can clearly tell them apart.

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?

It gives explicit when-to-use guidance: five specific moments to call it, and says 'not at the end and not never.' It also names alternatives (ingest, learn) and differentiates them, providing clear decision rules.

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