Skip to main content
Glama

remember

Store text as a HolographicBlock memory under a concept name using vector encoding with thermodynamic confidence gating. Preserves facts, decisions, and preferences for future AI agent sessions without cloud dependencies.

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 provided, the description carries full burden and thoroughly explains the encoding process, the ADR thermodynamic gate, CRS tiers (with numeric thresholds and meanings), and the destructive consequence of using forget+remember on an existing concept.

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?

The description is a single well-structured paragraph with no wasted words. It front-loads the core action, then provides when-to-call, mechanism, and a critical warning in logical order.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (no output schema, many siblings), the description covers purpose, usage, behavior, and warnings comprehensively. Minor gap: it does not mention the return value, but in context of memory storage tools, this is not critical. Otherwise complete.

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

Parameters3/5

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

The schema already provides clear descriptions for both parameters with 100% coverage. The tool description adds context about concept namespacing and text self-containment, but these are largely redundant with the schema's examples. Baseline 3 is appropriate as description adds minimal value 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 explicitly states 'Encode text and store it as a persistent HolographicBlock (.leg3) memory under a concept name,' which is a clear verb+resource. It distinguishes from siblings by warning not to use forget+remember for modification and pointing to mcp_engram_update.

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?

The description includes a dedicated 'WHEN TO CALL' section listing specific use cases (new facts, preferences, etc.) and explicitly instructs not to use forget+remember for modifications, directing to mcp_engram_update instead.

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