Skip to main content
Glama
Sign In
Rememb

Rememb

by LuizEduPP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rememb_read_page

Read a paginated slice of stored entries with optional section or tag filters, returning full content so you can summarize task-relevant facts after each page.

Instructions

Read a paginated slice of entries with optional section or tag filtering. Returns full entry content; summarize task-relevant facts in your working context after each page.

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

Input Schema

NameRequiredDescriptionDefault
tagNoOptional exact tag filter applied before pagination
limitNoMaximum entries to return
storeNoMemory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.global
offsetNoZero-based page offset
sectionNoOptional section filter: project, actions, systems, requests, user, context
sort_byNoSort order before paginationstorage
max_charsNoOptional mechanical cap on content characters per entry
descendingNoReverse the selected sort order
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": true,
-  "description": "Render a compact one-line summary per entry",
-  "type": "boolean"
-}
  2. Addedv0.4.11

TDQS

B3.4/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 does disclose that full entry content is returned and gives a useful working-context hint about summarizing per page. It is silent on ordering semantics, soft-deleted entries (include_deleted), and the max_chars truncation behavior, which matter for an agent interpreting results.

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?

Two tight sentences, front-loaded with the core action and followed by the return/context-handling note. No filler, though the second clause is advisory rather than definitional.

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, with 9 parameters, so the description should carry more weight than it does. It covers the return shape at a high level but leaves sort order, deletion inclusion, and multi-store behavior to the schema alone.

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 every parameter including store, sort_by, max_chars, and include_deleted is already documented. The description only echoes section/tag filtering and pagination, adding no syntax or precedence detail beyond the schema; baseline 3 applies.

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 and resource ('Read a paginated slice of entries') plus the two filtering axes, so the agent knows exactly what the call yields. It does not differentiate itself from close siblings such as rememb_read, rememb_recent, or rememb_search, leaving the boundary ambiguous.

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?

Pagination and filtering imply the usage (walk a large entry set page by page), but the description never says when to prefer this over rememb_read, rememb_recent, or rememb_search, nor any preconditions. Guidance is inferable rather than stated.

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