Skip to main content
Glama
Sign In
Rememb

Rememb

by LuizEduPP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rememb_edit

Update existing memory entries by ID or in batches, changing only the content, section, or tags you provide while leaving omitted fields unchanged.

Instructions

Update one existing memory entry by ID or multiple entries in one call via updates[]. Modifies only the fields provided (content, section, or tags) — omitted fields are unchanged. Non-destructive: entries are updated, not deleted and recreated. Use rememb_write to create new entries, rememb_delete to permanently remove them.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
tagsNoReplace tags
storeNoMemory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.global
contentNoNew content
sectionNoMove to different section
updatesNoBatch update payloads. Each item requires entry_id and at least one of content, section, or tags.
entry_idNoEntry ID (8 hex characters)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.20
    • addedInput schema / properties / store
      Added value: +{
+  "default": "global",
+  "description": "Memory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.",
+  "enum": [
+    "global"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / updates
      Added value: +{
+  "description": "Batch update payloads. Each item requires entry_id and at least one of content, section, or tags.",
+  "items": {
+    "properties": {
+      "content": {
+        "description": "New content",
+        "type": "string"
+      },
+      "entry_id": {
+        "description": "Entry ID (8 hex characters)",
+        "type": "string"
+      },
+      "section": {
+        "description": "Move to different section",
+        "enum": [
+          "project",
+          "actions",
+          "systems",
+          "requests",
+          "user",
+          "context"
+        ],
+        "type": "string"
+      },
+      "tags": {
+        "description": "Replace tags",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "entry_id"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedInput schema / required
      Removed value: -[
-  "entry_id"
-]
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

No annotations exist, so the description must carry the behavioral load; it discloses the key partial-update contract (omitted fields unchanged), that the operation is non-destructive/not delete-and-recreate, and that batching exists. It does not cover batch atomicity (what happens if one updates[] item fails), store scoping, or what the call returns.

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?

Three short sentences, front-loaded with the operation and the batch capability, then behavior, then sibling routing. No filler and nothing repeated from the schema.

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 6-parameter mutation tool with no annotations and no output schema, the description covers the mutation contract and alternatives well. Gaps remain around return values/confirmation, error behavior, and the entry_id-vs-updates[] selection rule, which an agent would have to infer.

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 schema already documents entry_id, content, section, tags, store, and updates[]. The description adds only framing (single vs batch, omitted-fields-unchanged), and stays silent on edge cases the schema leaves implicit, such as whether entry_id and updates[] are mutually exclusive or whether one must be supplied.

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) and resource (existing memory entry), plus the two invocation modes (single by ID, batch via updates[]). An agent can distinguish it from rememb_write/rememb_delete/rememb_restore 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 Guidelines4/5

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

Ends with explicit routing: use rememb_write to create, rememb_delete to permanently remove. It doesn't address other plausible overlaps (e.g. rememb_restore for reverting, or when to choose batch over repeated single calls), so it falls short of a full when/when-not mapping.

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