Skip to main content
Glama

Update Memory

update_memory
Idempotent

Correct or enhance stored memories by updating content, tags, importance, or metadata, preventing duplicate entries.

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
memory_idYesID of the memory to update (from store_memory or recall results)
contentNoNew content (replaces existing)
tagsNoNew tags (replaces existing)
importanceNoNew importance score
metadataNoNew metadata (merged with existing)
timestampNoOverride creation timestamp
updated_atNoExplicit update timestamp
last_accessedNoLast access timestamp
typeNoMemory type classification
confidenceNoConfidence score for the memory

Output Schema

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

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

Annotations already indicate mutability (readOnlyHint=false) and safety (destructiveHint=false, idempotentHint=true). The description adds context about correcting/enhancing memories instead of creating duplicates, aligning well with annotations and providing extra behavioral insight.

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?

The description is well-structured with clear headings, concise sentences, and relevant examples. No redundant information; every part adds value.

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?

For a tool with 10 parameters and nested objects, the description covers usage, purpose, and examples. Output schema exists so return values are documented elsewhere. Minor omission: the merging behavior for metadata is not explained in the description but is in the schema. Overall, quite complete.

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% with good parameter descriptions. The description lists key parameters (content, tags, importance, metadata) and provides examples but does not cover all 10 parameters. Given high schema coverage, baseline of 3 is appropriate.

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 updates existing memories' content, tags, importance, or metadata, and distinguishes from storing duplicates (store_memory). Purpose is specific and differentiates from siblings like delete_memory or store_memory.

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

Usage Guidelines5/5

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

Provides explicit when-to-use scenarios (correct inaccurate info, add tags, adjust importance, add metadata) and implies when not to use (avoid storing duplicates). This effectively guides the agent on appropriate context.

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