Skip to main content
Glama

store_memory

Store facts, preferences, and project details as long-term memories with auto-tagging and importance scoring for efficient retrieval.

Instructions

Store a new memory — fact, preference, project detail, note, or any information worth remembering. Tags and importance are auto-detected from content if not provided.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesUnique snake_case identifier (e.g. "user_name", "preferred_language", "project_deadline")
contentYesThe memory content — be descriptive and specific for better retrieval
tagsNoCategorization tags (auto-detected if omitted)
importanceNoImportance score 1-10 — higher = retrieved first (auto-scored if omitted)
Behavior2/5

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

No annotations provided, and the description does not disclose key behaviors such as whether it overwrites memories with the same key, side effects, or idempotency.

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?

Two concise sentences with the purpose front-loaded and no redundant information.

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

Completeness3/5

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

Given no output schema or annotations, the description could include more on success/error behavior and whether store_memory overwrites or fails on duplicate keys.

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?

The description adds value beyond the schema by recommending descriptive content for better retrieval and clarifying auto-detection for tags and importance, which is not in 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 the verb 'Store' and resource 'memory', with explicit examples of memory types (fact, preference, etc.), and it is distinct from sibling tools like forget_memory or update_memory.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description mentions auto-detection of tags and importance but does not specify when to use this tool over alternatives like update_memory for existing keys or when not to use it.

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/AIsofialuz/agent-memory-hub'

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