Skip to main content
Glama

mcp_engram_remember

Encode text into a persistent memory block under a unique concept name for recall in future sessions.

Instructions

Encode text and store it as a persistent HolographicBlock (.leg3) memory under a concept name. WHEN TO CALL: Any time you learn a new fact, decision, user preference, architecture detail, or solution you will need in a future session. If you would write it in a comment, store it here. WHAT IT DOES: Encodes text into a 256KB complex phase vector (q tensor), applies the ADR thermodynamic confidence gate, chains a BLAKE3 Merkle proof of lineage, and writes the block to the persistent NVMe manifold. New blocks start at CRS=1.0 (maximum confidence). CRS TIERS: 1.0=pinned/immortal | >=0.74=grounded fact (safe to act on) | >=0.50=working hypothesis (use with caution) | <0.50=uncertain (verify first). WARNING: To modify an existing concept use mcp_engram_update, NOT forget+remember. Calling forget+remember destroys the block's thermodynamic history permanently.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
conceptYesUnique snake_case identifier (e.g. 'api_auth_pattern', 'user_prefers_dark_mode'). Use namespacing for related concepts: 'project__component__detail'.
textYesThe text content to encode. Be specific and self-contained — this text must make sense when read in isolation in a future session.
Behavior5/5

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

With no annotations, the description fully discloses encoding to phase vector, ADR gate, Merkle proof, NVMe storage, CRS tiers, and destructive warning. No contradictions.

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?

Well-structured with clear sections (WHEN TO CALL, WHAT IT DOES, CRS TIERS, WARNING). Concise yet comprehensive, every sentence adds value.

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?

Given no output schema, the description covers purpose, usage, behavior, parameters, and warnings completely for this complex memory storage tool.

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% with descriptions. The description adds extra context about text being self-contained and concept using snake_case namespacing, going 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?

The description clearly states the tool encodes text as a persistent HolographicBlock under a concept name, with specific usage scenarios like new facts and decisions. It distinguishes from siblings mcp_engram_update and mcp_engram_forget.

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 'WHEN TO CALL' with concrete examples, warns against using forget+remember by directing to mcp_engram_update, and includes CRS tiers guiding when to act on stored memories.

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/staticroostermedia-arch/engram'

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