Skip to main content
Glama

Update a memory (audit-preserving)

update_memory

Correct a stored memory by ID while preserving an audit trail: the old value moves to history and the new value becomes active.

Instructions

Correct a memory by id (the #id from list_memories). Audit-preserving: the old value is retired to history and the new value becomes active — so the change still shows up in history.

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": {
      "memory_id": "<memory_id>",
      "new_value": "<new_value>"
    },
    "name": "update_memory"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idNo
user_idNodefault
agent_idNo
memory_idYes
new_valueYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is already structured. The description adds genuinely non-derivable behavior: the old value is retired into history rather than overwritten silently, which reconciles the mutation with destructiveHint=false and tells the agent the change remains auditable via `history`.

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, zero waste, with the operation and its identifier source front-loaded before the audit caveat. Nothing is repeated from the title or annotations.

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

Completeness3/5

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

An output schema exists, so return values need not be described, and the audit/history consequence is covered. However, for a mutation tool with five parameters the definition says nothing about failure modes (unknown id, cross-user access) or what the scope parameters do, leaving real gaps.

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

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with five parameters, so the description carries the full burden, yet it only explains `memory_id` (the `#id` from `list_memories`) and implicitly `new_value`. The three scoping parameters (`run_id`, `user_id`, `agent_id`) get no explanation of default behavior or which principal's memory is targeted — a meaningful gap for a multi-tenant store.

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 opens with a specific verb and resource: "Correct a memory by id", and points at `list_memories` as the source of the `#id`. An agent can tell this is an in-place edit rather than a create (`remember`) or removal (`forget`), though it never explicitly contrasts those siblings.

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 gives clear usage context: use this to correct an existing memory, and obtain the identifier from `list_memories`. There is no explicit when-not guidance (e.g., that removal belongs to `forget`/`delete` or that new entries belong to `remember`), so it stops short of full routing guidance.

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