Skip to main content
Glama
Sign In
Rememb

Rememb

by LuizEduPP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rememb_consolidate

Consolidate exact duplicate memory entries and merge their tags and access metadata; review near-duplicates with the agent before merging.

Instructions

Consolidate literal duplicate entries and merge metadata (tags and access data). Exact normalized-content match only; review near-duplicates with the agent before consolidating.

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_consolidate"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeNoMemory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.global
sectionNoOptional section filter: project, actions, systems, requests, user, context

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.4.20
    • removedInput schema / properties / mode
      Removed value: -{
-  "default": "exact",
-  "description": "Consolidation mode: exact (normalized content) or semantic (similarity threshold)",
-  "enum": [
-    "exact",
-    "semantic"
-  ],
-  "type": "string"
-}
    • removedInput schema / properties / similarity_threshold
      Removed value: -{
-  "default": 0.88,
-  "description": "Cosine similarity threshold used when mode is semantic (>0 and <=1)",
-  "type": "number"
-}
    • 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"
+}
  2. Addedv0.4.11

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that metadata (tags, access data) gets merged and that matching is exact-content based, but it doesn't state whether the operation is destructive, whether merged-away entries can be recovered (a rememb_restore sibling exists), or what the result looks like. Partial disclosure 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?

Two tight sentences, zero redundancy, with the core action and its matching scope front-loaded ahead of the cautionary guidance.

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?

No output schema and no annotations, so the description must cover behavior. It covers scope and the review workflow but omits what happens on consolidation (which entry survives, whether duplicates are deleted or archived, reversibility). Adequate but with real gaps for a mutation 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 description coverage is 100% and both parameters are enums documented in the schema (store, section). The description adds no detail beyond that, which is the expected baseline when the schema does all the work.

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 names a specific verb+resource (consolidate duplicate entries) and specifies exactly what is merged (tags and access data). It is clearly distinct from siblings like rememb_edit or rememb_delete, though it doesn't explicitly contrast itself with them.

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 a clear applicability condition — 'exact normalized-content match only' — and an explicit exclusion plus alternative workflow: review near-duplicates with the agent before consolidating. It doesn't name a specific sibling tool to use for the near-duplicate review, but the context is unambiguous.

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