Skip to main content
Glama

remember

Persist a new memory as a markdown file, commit it to git, and index it for immediate recall via hybrid search across LLM sessions.

Instructions

Persist a new memory: write memories/.md, commit, index — immediately recallable.

fact: the durable fact (short markdown, first sentence becomes the description). type: user|feedback|project|reference. name: optional kebab-slug filename. session/project: provenance trailers ($CLAUDE_CODE_SESSION_ID from Bash env / workspace dir); omitted when empty. If a near-duplicate memory exists it is returned instead of writing; force=true writes anyway. On success returns a stable mem_… id — pair recall → get_episode(id) to read it back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
factYes
nameNo
typeNoproject
forceNo
projectNo
sessionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations, the description fully discloses behavior: file persistence, deduplication logic, force flag, and return of stable mem_* ID.

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?

Every sentence adds value, but the description is slightly dense and could be structured into sections for easier parsing.

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 a 6-param tool with no annotations, the description provides complete context: behavior, return value, and integration with siblings.

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?

Despite 0% schema description coverage, the description adds complete meaning for all 6 parameters, including defaults, purpose, and provenance.

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 'Persist a new memory' and explains the write-commit-index workflow. It implicitly distinguishes from siblings recall and get_episode, clarifying the tool's unique role.

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?

It clearly says when to use the tool (to persist a new memory) and mentions near-duplicate handling, but lacks explicit when-not or alternative guidance.

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/sysangel/brain-mcp'

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