Skip to main content
Glama

remember

Store a memory with tags, importance, and type. Use a key to update facts without duplicates, ensuring recall returns the latest value.

Instructions

Store a memory (append-only; raw text is never edited afterward). tags group memories into cohorts; value (>=1) is its importance — higher-value memories outrank merely-similar ones at recall, and recall itself nudges value up. mtype ∈ {episodic, semantic, procedural} sets the decay prior — episodic (events) fades fast, semantic (durable facts) slow, procedural (rules / preferences) barely; pass it when you know the kind, else it's inferred.

Optional key is a deterministic (subject, relation) supersession key (e.g. "billing-api::auth-method"): storing a new value with the same key retires the old one so recall never returns the stale value — no similarity threshold, no extra LLM call. Use it for facts that get updated (config, prices, versions, status). Pass object = the asserted VALUE (e.g. "frankfurt") alongside key: with the echo guard on (default here), a later RE-STATEMENT of an already-retired value cannot resurrect it (a corrected fact stays corrected even if the old value is said again). Without object the guard still catches a verbatim restatement (text hash), but a reworded one needs the value in object to be caught. Set reaffirm=True to intentionally revert to a previously-retired value (an explicit change-of-mind, not an echo). Returns the new id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNo
tagsNo
textYes
mtypeNo
valueNo
objectNo
reaffirmNo
Behavior5/5

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

With no annotations, the description fully discloses behavior: append-only, recall nudges value, supersession with key, echo guard, decay based on mtype. All behavioral aspects are explained.

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 long but every sentence contributes valuable detail. It is front-loaded with the main purpose. Could be slightly more concise but justified by complexity.

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?

The tool has 7 parameters, no output schema, no annotations. The description covers all parameters, explains return value (new id), and provides comprehensive behavioral context. Fully meets the needs for selection and invocation.

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 add meaning. It does: explains 'tags' for grouping, 'value' importance and recall effect, 'mtype' with enum and decay, 'key' supersession, 'object' for echo guard, 'reaffirm' for intentional reverts. Adds substantial 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 clearly states 'Store a memory (append-only; raw text is never edited afterward)', which is a specific verb+resource. It distinguishes itself from siblings like 'forget' and 'recall' by focusing on storage.

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 detailed usage scenarios: explains when to use 'key' for supersession, when to pass 'object' for echo guard, and when to set 'reaffirm=True'. It covers context but does not explicitly contrast with alternative tools.

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/DanceNitra/mnemo'

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