Skip to main content
Glama

list_memories

Browse all stored memories with their slugs and rules to discover entries for retrieval or audit the full memory set. Filter by type or minimum priority.

Instructions

List all memories, returning slug + rule for each. CALL THIS: to browse what's stored, discover memory slugs for get_memory, or audit the full memory set. For finding relevant memories on a topic, use search_memories instead — it is faster and ranked.

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

Input Schema

NameRequiredDescriptionDefault
type_filterNofb=feedback (corrections, preferences, how the user likes to work), us=user (who the user is, their role, expertise, goals), pj=project (active projects, goals, decisions, deadlines), rf=reference (pointers to external systems, URLs, tools), cn=convention (code style, naming, architecture rules), lx=lesson (lessons learned, post-mortems, 'we got burned by X'), co=core (the per-project operating guide — which tools/skills/commands to reach for; always injected at session start, subordinate to the repo's own rules), tr=tracker (LIVE STATUS of exactly one entity — a deploy, draft, migration, campaign. One tracker per entity, slug '<entity>-status', tags naming the entity; UPDATE it by re-saving the same slug whenever the state changes. Trackers render as the status board at session start; memgit is the authority for this status, files are downstream)
min_priorityNoOnly return memories at or above this priority. 1=low (all memories), 2=medium+, 3=critical only. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.14.3

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden; it does disclose the return shape (slug + rule) and implies a complete, unfiltered enumeration ('audit the full memory set'), which is useful. It says nothing about volume limits, ordering, or pagination, so an agent cannot predict the cost of calling it on a large store.

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?

Two compact sentences, front-loaded with the verb and return shape, followed by usage triggers and then the alternative. No filler or restated title.

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 a simple zero-required-parameter read tool with full schema coverage, the description covers purpose, return contents, and sibling routing, which is nearly everything an agent needs. Only the absence of volume/ordering expectations keeps it from being fully complete given there is no output schema.

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 both parameters are heavily documented in-schema (the type_filter enum spells out all eight memory types and min_priority explains the 1/2/3 scale). The description adds no filter semantics of its own and in fact only describes the unfiltered 'list all' case, so baseline 3 applies.

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?

States a specific verb and resource ('List all memories') and even the return shape ('slug + rule for each'), which lets an agent tell it apart from search_memories and get_memory without opening any 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?

Explicitly names three when-to-use cases — browsing, discovering slugs for get_memory, and auditing the full set — and then names the alternative ('use search_memories instead') with the condition that selects it ('finding relevant memories on a topic') and why ('faster and ranked').

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