Skip to main content
Glama

List current memories

list_memories
Read-only

List a user's current active facts plus superseded, retracted, or archived history, with IDs for retrieving or updating active records.

Instructions

List the current active facts (the reconciled current beliefs) for a user, plus a history block of what was superseded / retracted / archived. Active rows show the #id for get/update.

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
run_idNo
user_idNodefault
agent_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral context the annotations do not: results include a separate history block of superseded/retracted/archived rows, which prevents an agent from misreading stale facts as current. It stops short of disclosing result volume, pagination, or scoping behavior.

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 short sentences with no filler; the core purpose and the history-block caveat are front-loaded, and the `#id` follow-up hint is packed efficiently at the end.

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?

An output schema exists, so the description is not obligated to explain return values, and the active-vs-history distinction is a helpful addition. However, for a three-parameter scoped list tool with zero schema coverage, the unexplained run_id and agent_id leave a material gap in what an agent needs in order to call it correctly.

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

Parameters2/5

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

Schema description coverage is 0% across three parameters, so the description must compensate and largely does not: it only says the listing is 'for a user', leaving run_id and agent_id completely unexplained in both schema and prose. With no defaults, no scoping semantics, and no note on what happens when a param is empty, an agent cannot reason about what each parameter filters.

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 ('List the current active facts') and adds a precise semantic gloss ('the reconciled current beliefs') plus the fact that a history block of superseded/retracted/archived rows is included. That is well beyond a restatement of the title. It does not name any sibling (e.g. 'history', 'recall', 'get_memory') to sharpen the boundary, so it falls short of a 5.

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?

Usage is only implied: the note that active rows show the `#id` for get/update quietly signals the natural follow-up workflow to get_memory/update_memory. There is no explicit statement of when to use this versus 'history', 'recall', or 'get_memory', and no exclusions or prerequisites.

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