Skip to main content
Glama

remember

Save new memories to a shared vault so all your AI assistants can access them. Use scopes for access control, supersede outdated facts, and templates for consistent structured records.

Instructions

Save a new memory to the user's vault so every other AI can see it too. Use for durable facts, preferences, project state — not throwaway chatter. Pass your identity in source (e.g. 'claude', 'chatgpt', 'gemini') so provenance and conflict detection work correctly across AIs. scopes (comma-separated, e.g. "legal" or "writing,coding") puts the memory in a compartment only clients granted that scope can read; omit it to make the memory general (visible to all) unless this client has a default scope. supersedes (a memory id or 8-char prefix) marks that this memory replaces an older one when a fact changes rather than adds (a move, a rename, an updated preference): the old memory is kept as history but hidden from recall, and history can then show what changed and when. template names a structure from the memory://templates resource and applies its type/tags/scopes defaults; fields is a JSON object filling that template's placeholders, e.g. {"who": "Ana", "date": "2026-07-25"}, which builds the content for you so repeated captures stay comparable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNo
typeNonote
fieldsNo
scopesNo
sourceNoai
contentYes
templateNo
supersedesNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries burden. It discloses that memories are visible to other AIs, provenance via source, compartmentalization via scopes, replacement via supersedes, and template usage. Does not mention idempotency or rate limits, but covers key behaviors.

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?

Paragraph is well-structured, front-loaded with main purpose, then explains parameters in sentence order. Slightly long but each sentence earns its place. Could be more compact but remains clear.

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 8 parameters, 0% schema coverage, no annotations, description covers workflow and parameter relationships. Does not explain return value but output schema exists. Complete enough for an AI to use correctly.

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?

With 0% schema coverage, description compensates fully. Explains all 8 parameters: source (identity), scopes (compartment), supersedes (replacement), template+fields (structured data), content, tags, type. Gives usage examples for fields and supersedes.

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 tool saves a memory to the user's vault for durable facts, preferences, project state. It distinguishes from siblings like recall, forget, history by focusing on creation. The verb 'Save' plus resource 'memory' is specific.

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?

Provides explicit context for use: durable facts not throwaway chatter. Explains how to use source, scopes, supersedes, template. Does not explicitly name alternatives like recall for retrieval or forget for deletion, but the context is clear.

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/darknodebros/EleSync'

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