Skip to main content
Glama
Sign In
agent-memory-os

agent-memory-os

by yamantaka520
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

memory_update

Update an existing memory's content, importance, confidence, or pin status without changing its ID. Correct facts, adjust rankings, or prevent forgetting.

Instructions

Update fields of an existing memory in place (keeps the same id).

    Use it to correct content, re-weight importance/confidence, or pin a memory so
    it is never forgotten. Only the fields you pass are changed. Returns the updated
    `id`, `content`, and `updated_at`, or an `{"error": ...}` object if the id does
    not exist.

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>"
    },
    "name": "memory_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
pinnedNoPin (true) to exempt the memory from decay/forgetting, or unpin (false). Omit to leave unchanged.
contentNoNew content text. Omit to leave unchanged.
memory_idYesId of the memory to modify.
confidenceNoNew confidence 0.0-1.0 (how sure the fact is true). Omit to leave unchanged.
importanceNoNew importance 0.0-1.0 (boosts ranking). Omit to leave unchanged.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.1.1
    • changedInput schema / properties / confidence / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / confidence / description
      Added value: +"New confidence 0.0-1.0 (how sure the fact is true). Omit to leave unchanged."
    • addedInput schema / properties / content / description
      Added value: +"New content text. Omit to leave unchanged."
    • changedInput schema / properties / importance / anyOf
      Previous value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 1,
+    "minimum": 0,
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / importance / description
      Added value: +"New importance 0.0-1.0 (boosts ranking). Omit to leave unchanged."
    • addedInput schema / properties / memory_id / description
      Added value: +"Id of the memory to modify."
    • addedInput schema / properties / pinned / description
      Added value: +"Pin (true) to exempt the memory from decay/forgetting, or unpin (false). Omit to leave unchanged."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

No annotations provided, so the description bears full burden. It discloses that only passed fields are changed, the return value includes id/content/updated_at or error for missing id, and pinning exempts from decay. This is transparent.

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 concise with three well-structured sentences, front-loading the main purpose. No unnecessary text.

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

Completeness5/5

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

Despite no output schema, the description explains return value and error case. It covers pinning behavior. Combined with full schema, the information is complete for an update tool.

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 each parameter well-described. The description adds minimal extra meaning beyond listing use cases, so baseline 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 it updates an existing memory in place, with specific use cases (correct content, re-weight importance/confidence, pin). It distinguishes from siblings like memory_add by noting 'keeps the same id'.

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?

The description implies usage scenarios (correction, re-weighting, pinning) but does not explicitly compare to siblings or state when not to use. However, the context is sufficient for an agent to decide.

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