Skip to main content
Glama

update_memory

Update an existing memory entry by key, modifying its content, tags, or importance score for better recall and organization.

Instructions

Update the content, tags, or importance of an existing memory by key.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyYesThe memory key to update
new_contentNoReplacement content (omit to keep existing)
tagsNoNew tag list — replaces existing tags
importanceNoNew importance score 1-10

Implementation Reference

  • Main handler for the 'update_memory' tool. Extracts key, new_content, tags, and importance from arguments, validates that the key exists, builds the updates object (using autoTags/autoImportance helpers), calls store.update(), and returns a formatted result.
    case 'update_memory': {
      const key = String(a['key'] ?? '').trim();
      if (!key) return err('key is required');
    
      const existing = store.byKey(key);
      if (!existing) return ok(`No memory found with key "${key}".`);
    
      const updates: Partial<Pick<Memory, 'content' | 'tags' | 'importance'>> = {};
      if (a['new_content'] !== undefined) updates.content = String(a['new_content']).trim();
      if (Array.isArray(a['tags'])) {
        updates.tags = autoTags(updates.content ?? existing.content, a['tags'] as string[]);
      }
      if (a['importance'] !== undefined) {
        updates.importance = autoImportance(updates.content ?? existing.content, Number(a['importance']));
      }
    
      const updated = store.update(key, updates);
      return ok(
        `Memory updated: ${key}\n` +
        `  Content:    ${updated!.content}\n` +
        `  Tags:       ${updated!.tags.join(', ') || '(none)'}\n` +
        `  Importance: ${updated!.importance}/10`
      );
    }
  • Tool registration with inputSchema defining the 'update_memory' tool's parameters: key (required string), new_content (optional string), tags (optional array of strings), importance (optional number).
      name: 'update_memory',
      description: 'Update the content, tags, or importance of an existing memory by key.',
      inputSchema: {
        type: 'object',
        properties: {
          key: { type: 'string', description: 'The memory key to update' },
          new_content: { type: 'string', description: 'Replacement content (omit to keep existing)' },
          tags: {
            type: 'array',
            items: { type: 'string' },
            description: 'New tag list — replaces existing tags',
          },
          importance: { type: 'number', description: 'New importance score 1-10' },
        },
        required: ['key'],
      },
    },
  • src/index.ts:23-24 (registration)
    The tool is registered via ListToolsRequestSchema handler which returns the tools array including 'update_memory'. The tools are defined as part of the MCP server's tool list.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools: [
  • The MemoryStore.update() method that performs the actual data mutation: finds memory by key, merges updates, sets updatedAt timestamp, persists to disk atomically, and returns the updated memory.
    update(key: string, updates: Partial<Pick<Memory, 'content' | 'tags' | 'importance'>>): Memory | null {
      const idx = this.data.memories.findIndex(m => m.key === key);
      if (idx === -1) return null;
      this.data.memories[idx] = { ...this.data.memories[idx], ...updates, updatedAt: new Date().toISOString() };
      this.persist();
      return this.data.memories[idx];
    }
  • autoTags helper used by the update handler to auto-detect tag categories from content (preserving user-provided tags).
    export function autoTags(content: string, provided: string[]): string[] {
      const lower = content.toLowerCase();
      const tags = new Set(provided.map(t => t.toLowerCase().trim()).filter(Boolean));
    
      for (const [category, signals] of Object.entries(SIGNALS)) {
        if (signals.some(s => lower.includes(s))) {
          tags.add(category);
        }
      }
    
      return Array.from(tags);
    }
Behavior2/5

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

No annotations are present, so the description must fully disclose behavior. It states 'update' but does not clarify partial vs full replacement semantics for tags or importance, nor does it mention side effects, permissions, or return value. The schema clarifies 'tags' replaces, but the description omits this detail.

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 a single sentence with key information front-loaded. It is concise but could include a brief note on usage or behavior without becoming verbose.

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 no output schema and no annotations, the description is too minimal. It does not explain the return value, confirm the key must exist, or differentiate from sibling tools. The 4-parameter complexity demands more context for correct invocation.

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?

Input schema coverage is 100%, so parameters are already documented. The description lists 'content, tags, or importance' as updatable fields, providing a quick overview but no additional semantic value beyond the 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 specifies the verb 'update', the resource 'memory', and the mutable attributes 'content, tags, or importance'. It differentiates from sibling tools like 'store_memory' (create) and 'forget_memory' (delete) by explicitly stating it operates on an existing memory.

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 provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., memory must exist), nor does it contrast with 'store_memory' (for new memories) or 'forget_memory' (for deletion). The agent is left to infer usage 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/AIsofialuz/agent-memory-hub'

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