Skip to main content
Glama
Doucs91

Hivelore

by Doucs91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

mem_update

Update an existing memory's body, tags, or anchors in place when its content is outdated or incomplete, preserving its ID, usage history, and read count.

Instructions

Update the body, tags, or anchor of an existing memory in-place.

USE WHEN a memory exists but its content has become outdated or incomplete. This preserves the memory's id, usage history, and read_count.

For evolving memories that you will update repeatedly, use mem_save with a topic key instead (topic-upsert pattern).

PARAMETERS: id — full memory id to update body — new Markdown content (replaces existing body) tags — new tag list (replaces existing tags) paths — new anchor paths (replaces existing paths) symbols — new anchor symbols (replaces existing symbols)

RETURNS: { id, file_path, updated_fields: string[] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesId of the memory to update
bodyNoNew Markdown body — replaces the existing body
tagsNoNew tags array — fully replaces existing tags
pathsNoNew anchor paths — fully replaces existing anchor.paths
authorNoNew author handle or email
checksNo
commitNoNew anchor commit SHA
domainNoNew domain label
symbolsNoNew anchor symbols — fully replaces existing anchor.symbols
evidenceNo
supersedesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.65.0
    • addedInput schema / properties / checks
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "contains": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "excludes": {
+        "minLength": 1,
+        "type": "string"
+      },
+      "path": {
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "path"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / evidence
      Added value: +{
+  "enum": [
+    "hypothesis",
+    "observed",
+    "reproduced",
+    "tested"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / supersedes
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Addedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that id, usage history, and read_count are preserved, and that body/tags/paths/symbols fully replace prior values. It does not cover authorization, error behavior, or reversibility, which is a modest gap for a mutation tool.

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?

Front-loads the action, then the use case, then the alternative and metadata, in four tight blocks with no wasted prose. Labels (USE WHEN, PARAMETERS, RETURNS) make it scannable.

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 mutation tool with no annotations and no output schema, it supplies a RETURNS shape and the key preservation guarantee. The incomplete parameter coverage (six params undocumented in the description) leaves small holes, though the schema carries most of that.

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 73% and the schema already states replacement semantics for body/tags/paths/symbols, so the description's parameter list largely restates structured data. It adds no format or constraint detail (e.g. tag dedup, path anchoring) and omits six of the eleven parameters (author, checks, commit, domain, evidence, supersedes) entirely.

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 (memory) and the in-place nature, and distinguishes itself from mem_save via the topic-upsert note. An agent can pick this apart from mem_save/mem_get without opening a schema.

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

Usage Guidelines5/5

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

Explicit 'USE WHEN a memory exists but its content has become outdated or incomplete' gives the trigger condition, and it names the alternative (mem_save with topic key) with the exact scenario that selects it (repeated updates / topic-upsert pattern).

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