Skip to main content
Glama
n3wth

r3 (Recall)

by n3wth
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_all_memories

Read-onlyIdempotent

List all stored memories for a user with pagination to browse or perform bulk operations. Retrieve total counts, offsets, and cache stats in a read-only, cache-first response.

Instructions

List all memories for a user with pagination. Use for browsing or bulk operations. For content search, use search_memory instead. Cache-first by default. Large result sets are automatically truncated. Read-only. Returns: {total, limit, offset, returned, hasMore, source, memories[]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum memories per page. Range: 1-500. Default: 100. Use with offset for pagination.
offsetNoNumber of memories to skip. Use for pagination: page N = offset (N-1)*limit. Default: 0.
user_idNoUser namespace to list. Default: "oliver".
prefer_cacheNotrue: return cached memories (faster). false: fetch from storage (fresher). Default: true.
include_cache_statsNoAppend cache statistics to response. Useful for monitoring. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changedv1.3.2
    • removedInput schema / properties / include_cache_stats / default
      Removed value: -true
    • changedInput schema / properties / include_cache_stats / description
      Previous value: -"Include Redis cache statistics"New value: +"Append cache statistics to response. Useful for monitoring. Default: true."
    • removedInput schema / properties / limit / default
      Removed value: -100
    • changedInput schema / properties / limit / description
      Previous value: -"Number of memories to return (max 500)"New value: +"Maximum memories per page. Range: 1-500. Default: 100. Use with offset for pagination."
    • removedInput schema / properties / offset / default
      Removed value: -0
    • changedInput schema / properties / offset / description
      Previous value: -"Number of memories to skip for pagination"New value: +"Number of memories to skip. Use for pagination: page N = offset (N-1)*limit. Default: 0."
    • removedInput schema / properties / prefer_cache / default
      Removed value: -true
    • changedInput schema / properties / prefer_cache / description
      Previous value: -"Use cached memories first to avoid slow API calls"New value: +"true: return cached memories (faster). false: fetch from storage (fresher). Default: true."
    • removedInput schema / properties / user_id / default
      Removed value: -"oliver"
    • addedInput schema / properties / user_id / description
      Added value: +"User namespace to list. Default: \"oliver\"."
  2. First observedv1.3.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context beyond the annotations: cache-first default and automatic truncation of large result sets. It does not contradict the annotations, but could have expanded slightly on cache implications.

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?

The description is three succinct sentences with no wasted words. It front-loads the core action, then gives usage guidance, behavioral notes, and return shape, all in a logical and efficient structure.

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?

The description includes the essential return shape ({total, limit, offset, returned, hasMore, source, memories[]}), which compensates for the absence of an output schema. Combined with complete parameter documentation and explicit sibling routing, an agent has everything needed to invoke this tool correctly.

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 each parameter is already clearly documented with ranges, defaults, and usage semantics. The description mentions pagination generally but adds no parameter-level meaning beyond what the schema provides, matching the baseline expected score.

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?

The description states the specific verb 'List' and resource 'all memories for a user with pagination,' clearly defining the tool's scope. It also distinguishes the tool from its sibling search_memory, so an agent can differentiate them immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

The description explicitly states when to use this tool ('for browsing or bulk operations') and directs the agent to an alternative when needed ('For content search, use search_memory instead'). This is precise routing guidance with no ambiguity.

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