Skip to main content
Glama

update_memory

Correct an existing memory's content, kind, or importance using its recall id; auto re-embedding keeps semantic search accurate.

Instructions

Correct an existing memory: replace its content (auto re-embedded so semantic search stays accurate), change its kind, or adjust importance. Pass the memory id from recall.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "update_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMemory id from recall
kindNoMemory type: decision, fact, preference, open task (task_pending), finished task (task_done), fixed error (error_fixed) or general context
contentNoReplacement content, short and dense
importanceNoNew importance, 0 to 1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.16.1
    • addedInput schema / properties / importance / description
      Added value: +"New importance, 0 to 1"
    • addedInput schema / properties / kind / description
      Added value: +"Memory type: decision, fact, preference, open task (task_pending), finished task (task_done), fixed error (error_fixed) or general context"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose a real side effect: content is auto re-embedded so semantic search stays accurate. It also implies partial updates ('replace... change... or adjust'), so the agent knows unmentioned fields are untouched. It does not say what the call returns or what happens if the id is invalid.

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?

Two tight sentences, front-loaded with the action, followed by the field options and the id sourcing note. Nothing is wasted and the re-embedding caveat is folded in parenthetically rather than sprawling.

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 4-parameter mutation tool with a fully documented schema and no sibling ambiguity, the description covers what is changed and the meaningful side effect. The remaining gap is outcome behavior — what the response looks like after an update or what occurs on a bad id — which matters slightly more since no output schema exists.

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 the enum values, the 0-to-1 importance range, and id sourcing are already documented. The description reinforces that id comes from recall and that content is the replacement payload, but adds no format or validation detail beyond the schema. Baseline 3 applies.

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 gives a specific verb ('Correct') plus the resource ('an existing memory') and enumerates the three mutable fields (content, kind, importance), so an agent can tell it apart from creation tools like remember. It doesn't explicitly name a sibling it is not, but 'existing' versus new is clear.

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?

It states the context clearly — use this to correct an existing memory, not to store a new one — and tells the agent where the id comes from ('Pass the memory id from recall'). No explicit when-not or named alternative, which holds it below a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.