Skip to main content
Glama
Sign In
Rememb

Rememb

by LuizEduPP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

rememb_stats

Returns memory usage statistics such as total entries, size in KB, oldest and newest entry dates, and per-section counts. Use it to review a memory store or decide whether cleanup is needed.

Instructions

Return memory usage statistics: total entries, size in KB, oldest and newest entry dates, and count per section. Safe, read-only operation with no side effects. Use to give the user an overview of their memory store or to decide if cleanup is needed.

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

Input Schema

NameRequiredDescriptionDefault
storeNoMemory store id. 'global' is the ~/.rememb store. Other ids are project stores passed via repeated --project MCP args.global

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field 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"
+}
  2. Addedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full behavioral burden; it does declare 'safe, read-only operation with no side effects' and enumerates the return fields, which is meaningful disclosure. It omits cost/performance, whether the store must already exist, and any pagination or truncation behavior for large stores.

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 sentences, front-loaded with the concrete metrics and followed by purpose. Minor redundancy between 'safe, read-only' and 'no side effects', but nothing wasteful or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter stats tool with no output schema, the description names exactly which statistics come back and when to reach for it. Nothing an agent needs in order to call this correctly is missing.

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?

Only one optional parameter and schema coverage is 100%, with the schema fully explaining 'global' vs project store ids. The description adds nothing about the store parameter (e.g. whether stats are scoped strictly to that store), so the 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?

Specific verb (return) plus resource (memory usage statistics) with the returned metrics enumerated: totals, size in KB, oldest/newest dates, per-section counts. That distinguishes it from list/read siblings such as rememb_list_stores or rememb_recent, 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 Guidelines4/5

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

Gives two concrete use cases: overview of the user's memory store and deciding whether cleanup is needed. It does not state when not to use it or name an alternative (e.g. rememb_list_stores for enumerating stores or rememb_clear for cleanup), so routing is clear but not exhaustive.

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