Skip to main content
Glama
Sign In
Rememb

Rememb

by LuizEduPP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rememb_read

Read stored memory entries or filter them by section to retrieve project, user, and context facts; this read-only operation has no side effects.

Instructions

Read all memory entries or filter by section. Safe, read-only operation with no side effects. Returns full entry content; summarize task-relevant facts in your working context after large reads.

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

Input Schema

NameRequiredDescriptionDefault
storeNoMemory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.global
sectionNoFilter by section: project, actions, systems, requests, user, context
max_charsNoOptional mechanical cap on content characters per entry
include_deletedNoInclude soft-deleted entries in the response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.4.20
    • addedInput schema / properties / include_deleted
      Added value: +{
+  "default": false,
+  "description": "Include soft-deleted entries in the response",
+  "type": "boolean"
+}
    • changedInput schema / properties / max_chars / description
      Previous value: -"Maximum characters of content to include per entry"New value: +"Optional mechanical cap on content characters per entry"
    • 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"
+}
    • removedInput schema / properties / summary_only
      Removed value: -{
-  "default": false,
-  "description": "Render a compact one-line summary per entry",
-  "type": "boolean"
-}
  2. Changed2 schema fields changedv0.4.11
    • addedInput schema / properties / max_chars
      Added value: +{
+  "description": "Maximum characters of content to include per entry",
+  "type": "integer"
+}
    • addedInput schema / properties / summary_only
      Added value: +{
+  "default": false,
+  "description": "Render a compact one-line summary per entry",
+  "type": "boolean"
+}
  3. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it declares read-only/side-effect-free behavior and states it returns full entry content. It omits pagination behavior and how include_deleted interacts with results, keeping it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the core purpose front-loaded and no filler. Minor overlap between the opening verb phrase and the tool name, but nothing wasted.

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 no output schema and full schema coverage, the remaining burden is behavioral: safety and return shape are covered, and the large-read guidance is a useful extra. Only pagination/large-result handling and deleted-entry semantics are left 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 all four parameters are already documented in the schema, including the section enum and the max_chars cap. The description only restates section filtering and adds no extra semantics such as max_chars interaction with truncation or store selection beyond 'global'.

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?

States a specific verb ('Read') and resource ('memory entries') plus the primary scoping mechanism ('filter by section'). An agent can infer it is the collection-level reader rather than the single-item rememb_get, though no sibling is named explicitly.

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?

Implies usage ('read all ... or filter by section') but gives no explicit when-to-use/when-not guidance versus rememb_get, rememb_search, or rememb_recent, which are the natural alternatives for this tool. The closing advice about summarizing after large reads is the only contextual guidance.

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