Skip to main content
Glama
yamantaka520

agent-memory-os

memory_add

Store a durable memory such as a user preference or project fact that persists across sessions and becomes immediately searchable.

Instructions

Store a durable memory that will survive across sessions.

    Use this to remember a user preference, project fact, decision, procedure,
    or lesson worth recalling later — not transient chat. Content is de-duplicated
    softly by the engine and becomes searchable immediately. Returns the new
    memory's stable `id` and stored `content`.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoKind of memory: 'preference', 'fact', 'procedure', 'environment', 'decision', 'warning', or 'note'.note
ownerNoOwner id the memory belongs to. Defaults to this server's AGENT_MEMORY_AGENT_ID, else 'default'.
scopeNoLifecycle label used for graph coloring and filtering: 'user', 'agent', 'project', 'team', or 'global'. Does NOT set access control (use visibility for that).user
contentYesThe fact to remember, as a self-contained sentence (e.g. 'The user prefers dark mode.'). Write it so it makes sense on its own in a future session.
Behavior4/5

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

With no annotations, the description does well by disclosing durability, searchability, soft de-duplication, and return value. It could add more about potential overwrite behavior or auth needs, but covers the key behavioral traits for a create operation.

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 extremely concise, using two sentences to convey purpose, usage context, and return information. It is front-loaded with the core action and avoids any fluff or redundancy.

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 clearly states what the tool returns (stable id and content). It covers all necessary aspects for a create tool: what it stores, behavior, and output, making it fully self-contained.

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%, so baseline is 3. The description adds value by advising to write content as a self-contained sentence, which adds semantic context beyond the schema. It also implies the content parameter is the primary input.

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 verb 'store' and resource 'memory', and distinguishes from transient chat. It specifies the type of content (preference, fact, etc.) and mentions de-duplication and searchability, differentiating it from sibling tools like memory_search or memory_update.

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?

The description provides explicit context on when to use (durable facts) and what not to store (transient chat). However, it does not explicitly name alternative sibling tools for comparison, which would enhance 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/yamantaka520/Agent-Memory-OS'

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