Skip to main content
Glama

store

Store a memory with optional context metadata.

Instructions

Store a memory with optional context metadata.

Args: content: The information to remember. project: Cortical region — project name for scoped retrieval. language: Programming language context. scope: Engram cluster — domain scope (e.g. "auth", "database"). memory_type: Memory system (episodic/semantic/procedural/prospective). tags: Comma-separated tags for categorization. source: Which tool stored this ("copilot", "cursor", etc.). overwrite: If True and content is a near-duplicate of an existing memory, replace the old memory instead of rejecting. The response will include "replaced": <old_parent_id> and "status": "updated". agent_id: Namespace identifier for the storing agent or bot. Memories tagged with an agent_id are only returned when the same agent_id is supplied at recall time. relations: JSON-encoded list of [subject, predicate, object] triples to assert as relationship edges immediately, e.g. '[["AuthService","depends_on","JWTHelper"]]'. Malformed input is silently ignored so it never blocks the store.

Returns: JSON with memory ID on success, or rejection reason.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
scopeNo
sourceNo
contentYes
projectNo
agent_idNo
languageNo
overwriteNo
relationsNo
memory_typeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden. It explains overwrite behavior, silent failure for malformed relations, agent_id scoping, and return format. This is comprehensive and avoids contradictions.

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 well-structured with Args and Returns sections and is front-loaded with the main purpose. It is somewhat lengthy but justified by 10 parameters. Every sentence adds value, so no waste.

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 the complexity (10 params, no annotations, sibling tools), the description covers purpose, all parameters with detailed semantics, return values, and edge cases (malformed inputs). It is comprehensive enough for an agent to correctly select and invoke the tool.

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. It thoroughly explains all 10 parameters, including overwrite's response details, relations format with error handling, and agent_id scoping. This adds significant meaning beyond the 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 'Store a memory with optional context metadata,' which is a specific verb+resource. It distinguishes from sibling tools like recall, forget, and ingest by focusing on storage creation.

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 clear context for storing memories but does not explicitly state when to use this tool versus alternatives (e.g., ingest for bulk import). However, the purpose is self-evident and adequately differentiated by name and siblings.

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/et-do/myelin'

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