Skip to main content
Glama

Update Memory

update_memory
Idempotent

Update stored memories to correct inaccuracies or add missing details. Modify content, tags, importance, and metadata to keep information accurate.

Instructions

Update an existing memory's content, tags, importance, or metadata. Use this to correct or enhance memories rather than storing duplicates.

When to use:

  • To correct inaccurate information in a memory

  • To add tags that were forgotten

  • To adjust importance based on new understanding

  • To add metadata after the fact

Examples:

  • update_memory({ memory_id: "abc123", importance: 0.95 }) // Increase importance

  • update_memory({ memory_id: "abc123", tags: ["project-x", "critical", "auth"] }) // Add tags

  • update_memory({ memory_id: "abc123", content: "Updated: PostgreSQL chosen for ACID + team expertise" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsNoNew tags (replaces existing)
typeNoMemory type classification
contentNoNew content (replaces existing)
t_validNoISO 8601 timestamp when the memory becomes valid
metadataNoNew metadata (merged with existing)
memory_idYesID of the memory to update (from store_memory or recall results)
t_invalidNoISO 8601 timestamp when the memory expires or was superseded
timestampNoOverride creation timestamp
confidenceNoConfidence score for the memory
importanceNoNew importance score
updated_atNoExplicit update timestamp
last_accessedNoLast access timestamp

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
messageYesConfirmation message
memory_idYesID of the updated memory
Behavior3/5

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

Annotations indicate idempotentHint=true and destructiveHint=false, which the description does not contradict. The description adds context about 'correct or enhance' but does not detail update semantics like overwriting vs merging (e.g., metadata merges per schema). Since annotations cover the core behavioral traits, the description provides moderate added value.

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 a clear header, a bulleted 'When to use' list, and examples. It is concise (5 sentences plus examples) and front-loaded. Slightly more could be trimmed but overall efficient.

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 the tool has 12 parameters (all documented in schema), an output schema exists, and annotations are present, the description provides sufficient context for the main purpose and use cases. It lacks error behavior details but these are not critical given the schema coverage.

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 description coverage is 100%, so the baseline is 3. The description does not add additional meaning beyond the schema; it only groups parameters in the first sentence. Examples illustrate some parameters but no new semantics.

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 'Update' and the resource 'memory', and lists the updateable fields (content, tags, importance, metadata). It distinguishes from the sibling tool 'store_memory' by advising against storing duplicates.

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 'When to use' section provides four explicit use cases (correct inaccuracies, add tags, adjust importance, add metadata) and implicitly advises against using store_memory for updates. However, it does not mention when not to use this tool (e.g., if memory should be deleted entirely) or prerequisites (e.g., memory must exist).

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/verygoodplugins/mcp-automem'

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