Skip to main content
Glama

memory_list

Read-only

Browse and paginate stored memories with optional tag, type, agent, or inactivity filters to see what is saved.

Instructions

List and browse memories with pagination and optional filters.

USE THIS WHEN:

  • User wants to browse all memories ("show me my memories", "list everything")

  • Need to paginate through large result sets

  • Filter by tag OR memory type for categorical browsing

  • User asks "what do I have stored", "browse my memories"

Unlike memory_search (semantic search), this does categorical listing/filtering.

PAGINATION:

  • page: 1-based page number (default: 1)

  • page_size: Results per page (default: 20, max: 100)

FILTERS (combine with AND logic):

  • tags: Filter to memories with matching tags

  • tag_match: "any" (OR, default) or "all" (AND) — controls how multiple tags are matched

  • memory_type: Filter by type (note, reference, decision, etc.)

  • stale_days: Filter to memories not accessed in the last N days

Examples: {} // List first 20 memories {"page": 2, "page_size": 50} {"tags": ["python", "reference"]} {"tags": ["python", "reference"], "tag_match": "all"} {"memory_type": "decision", "page_size": 10} {"tags": ["important"], "memory_type": "note"} {"stale_days": 30} // Memories not accessed in 30 days {"stale_days": 7, "tags": ["archived"]} // Stale archived memories

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": "memory_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (1-based)
tagsNoFilter by tags (returns memories with ANY of these tags by default, use tag_match to control)
storeNoTarget store partition (default: 'default'). Use 'docs' for documents, 'all' for cross-store search.
agent_idNoFilter to memories authored by this agent (matches metadata.agent_id or the agent:<id> tag). Opt-in; omit to search all agents.
page_sizeNoResults per page
tag_matchNoMatch ANY tag (OR, default) or ALL tags (AND)any
stale_daysNoFilter to memories not accessed in the last N days. Uses COALESCE(last_accessed, created_at) for memories never read. Currently supported on sqlite-vec backend only.
memory_typeNoFilter by memory type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.6/5.0
Behavior4/5

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

readOnlyHint=true already establishes the safety profile, so the description's job is additive context, and it delivers: filter combination is spelled out as AND logic, tag_match governs OR vs AND, and pagination defaults (1 / 20, max 100) are stated. It does not describe ordering or the shape of returned records, which is the remaining gap for a tool with no output schema.

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?

Purpose is front-loaded, then usage, then pagination, filters and examples in a scannable hierarchy. The examples are compact JSON with inline comments and each one demonstrates a distinct filter combination rather than restating the filter list.

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?

For an 8-parameter, zero-required, read-only listing tool, the description supplies everything needed to construct a correct call, including defaults and filter interaction rules. Only the undocumented store/agent_id filters and the absence of any statement about result ordering or return shape keep it short of complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the worked examples add real meaning beyond per-field docs by showing how tags, tag_match, memory_type and stale_days compose in practice. It does omit two of the eight parameters entirely — store (notably the 'all' cross-store option) and agent_id — which keeps it from a 5.

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 opening line gives a specific verb and resource ('List and browse memories') plus the scope modifiers (pagination, optional filters). It explicitly contrasts itself with memory_search, so an agent can separate categorical listing from semantic retrieval without opening either schema.

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 'USE THIS WHEN' block enumerates concrete user phrasings ('show me my memories', 'what do I have stored') and the pagination/filtering scenarios that select this tool. It names the alternative (memory_search) and states the distinguishing condition — semantic search vs categorical listing — leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.