Skip to main content
Glama
vbcherepanov

total-agent-memory

by vbcherepanov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

memory_update

Destructive

Revise saved knowledge by replacing a record via id or search query, creating a new version that supersedes the old one.

Instructions

Update existing knowledge. Replaces the record id, or the best match for find (within project when given): supersedes it and creates a new version.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoExact record to replace; takes precedence over find
findNoSearch query to find the old knowledge (when no id)
reasonNoWhy updating
projectNoLimit the find search to this project
new_contentYesNew content to replace with

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv14.7.0
    • changedInput schema / properties / find / description
      Previous value: -"Search query to find the old knowledge"New value: +"Search query to find the old knowledge (when no id)"
    • addedInput schema / properties / id
      Added value: +{
+  "description": "Exact record to replace; takes precedence over find",
+  "type": "integer"
+}
    • addedInput schema / properties / project
      Added value: +{
+  "description": "Limit the find search to this project",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "find",
-  "new_content"
-]New value: +[
+  "new_content"
+]
  2. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds meaningful context beyond that: the operation is non-destructive in the sense that it supersedes and versions rather than erasing, which an agent needs to understand before calling a 'destructive' tool. It does not cover auth requirements or whether old versions remain retrievable.

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?

A single dense sentence with the core mechanism front-loaded and zero filler; everything after the first clause sharpens selection between id and find.

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?

With 5 parameters, full schema coverage, and safety annotations present, the definition covers what an agent needs to invoke it. The only gap is what happens to the superseded record (retrievable via memory_history?), which the description leaves implicit.

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 restates the id-over-find precedence, which the schema already documents per-parameter, and adds no format or constraint detail beyond that.

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?

States a specific verb (update) plus resource (existing knowledge) and explains the mechanism: replaces a record and supersedes it with a new version. This clearly distinguishes it from memory_save (create) and memory_delete (remove) among the many memory_* siblings.

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

Usage Guidelines3/5

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

The description gives useful selection context for its own inputs (id takes precedence over find; project narrows find), but says nothing about when to choose this tool over memory_save, memory_delete, or memory_consolidate. Usage is implied rather than stated.

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

Deploy Server

Other Tools