Unified Memory MCP

List Memories

list_memories

Read-onlyIdempotent

Retrieve recent active memories with optional filters for type, tags, scope, and namespace. Excludes sensitive and expired memories by default.

Instructions

List recent active memories with optional filters. Sensitive memories are excluded by default.

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

Name	Required	Description
`tags`	No	Require all listed tags.
`type`	No	Restrict to a memory type.
`limit`	No	Maximum results, up to 100.
`scope`	No	Restrict to a scope.
`namespace`	No	Restrict to a namespace.
`include_expired`	No	Include expired memories.
`include_sensitive`	No	Include memories marked sensitive.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's safe. Description adds that sensitive memories are excluded by default and focuses on recent active ones, but lacks detail on ordering or default limit.

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?

Single sentence, front-loaded with the main action. Efficient but could be structured with bullet points for clarity.

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?

Given 7 parameters and no output schema, the description covers core functionality but misses details like default limit, ordering, or what 'recent' means. Adequate but not comprehensive.

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 coverage is 100% with descriptions for all 7 parameters. Description adds no additional parameter information beyond 'with optional filters', so baseline 3 is appropriate.

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?

Description clearly states it lists recent active memories with optional filters, distinguishing from sibling tools like search_memory (search vs list) and remember (create).

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives like search_memory. Does not specify when to include sensitive or expired memories.

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

Deploy Server