Skip to main content
Glama

save_memory

Idempotent

Save a memory entry to a persistent store for secure retrieval. Keep information organized with tags and optional agent isolation to ensure context-aware recall.

Instructions

Save a memory entry to the persistent store. Alias of save_to_synapse.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoTags for categorization.
contentYesThe memory content to store securely.
agent_idNoAgent identifier for memory isolation.
force_intentNoMANUAL OVERRIDE ONLY — use apenas quando você (humano) quer forçar explicitamente a classificação de intenção. Valores reconhecidos: preference | fact | procedural | bio | critical | operational | strategic | compliance | security | system_directive | clinical | general | ephemeral. Se não tiver certeza, NÃO preencha este campo — o sistema classifica automaticamente. Valores não reconhecidos são ignorados silenciosamente e retornados em warnings.
intent_reasonNoAuditable reason for forcing intent classification. Max 500 characters. Ignored if force_intent is absent.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
scopeYes
storedYes
Behavior2/5

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

The description adds 'persistent store' but otherwise repeats what annotations already provide (write operation via 'Save', idempotentHint via implication). It does not disclose behavioral traits like idempotency behavior, overwrite policy, or any side effects beyond the annotation's idempotentHint.

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?

Two short sentences, front-loaded with the core purpose, and every sentence serves a purpose (purpose + alias clarification). Could be more tightly integrated but efficient overall.

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

Completeness2/5

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

With 5 parameters, a complex force_intent field, and an output schema, the description is too sparse. It omits guidance on parameter usage (e.g., agent_id for isolation, force_intent manual override) and does not set expectations for results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/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 does not provide any additional meaning beyond the schema for the 5 parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 entry to the persistent store, providing a specific verb and resource. However, it does not differentiate from sibling tools like store_memory or recall_memory, merely noting it is an alias of save_to_synapse.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool vs alternatives. The description only mentions it is an alias of save_to_synapse, but does not explain the distinction between the two or when to pick one over the other (e.g., store_memory).

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/SynapseLayer/synapse-layer'

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