Memlord

Overview Schema Source Related Servers Discussions Admin

list_memories

Read-only

Browse and enumerate all stored memories, ordered newest first, to audit or review without a specific search query. Returns full content, not snippets.

Instructions

Browse all memories ordered by creation date (newest first). Returns full content (not snippets). Use to enumerate or audit without a specific query.

Input Schema

TableJSON Schema

Name	Required	Description
`tag`	No	Case-insensitive exact match on a single tag name
`page`	No
`page_size`	No
`memory_type`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No
`items`	No
`total`	No
`page_size`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.2.9Sep 27, 2026

changedInput schema / properties / memory_type / anyOf

Previous value: -[
-  {
-    "description": "fact: established fact about user, project, or system.\npreference: user's likes, dislikes, habits.\ninstruction: persistent rule Claude must follow.\nfeedback: evaluation of Claude's output.\ndecision: a choice made with reasoning ('chose X over Y because Z').",
-    "enum": [
-      "fact",
-      "preference",
-      "instruction",
-      "feedback",
-      "decision"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "fact: established fact about user, project, or system.\npreference: user's likes, dislikes, habits.\ninstruction: persistent rule Claude must follow.\nfeedback: evaluation of Claude's output.\ndecision: a choice made with reasoning ('chose X over Y because Z').\ninsight: consolidated conclusion distilled from several existing memories.",
+    "enum": [
+      "fact",
+      "preference",
+      "instruction",
+      "feedback",
+      "decision",
+      "insight"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / items / items / properties / expires_at

Added value: +{
+  "anyOf": [
+    {
+      "format": "date-time",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Expires At"
+}

changedOutput schema / properties / items / items / properties / memory_type / description

Previous value: -"fact: established fact about user, project, or system.\npreference: user's likes, dislikes, habits.\ninstruction: persistent rule Claude must follow.\nfeedback: evaluation of Claude's output.\ndecision: a choice made with reasoning ('chose X over Y because Z')."New value: +"fact: established fact about user, project, or system.\npreference: user's likes, dislikes, habits.\ninstruction: persistent rule Claude must follow.\nfeedback: evaluation of Claude's output.\ndecision: a choice made with reasoning ('chose X over Y because Z').\ninsight: consolidated conclusion distilled from several existing memories."

changedOutput schema / properties / items / items / properties / memory_type / enum

Previous value: -[
-  "fact",
-  "preference",
-  "instruction",
-  "feedback",
-  "decision"
-]New value: +[
+  "fact",
+  "preference",
+  "instruction",
+  "feedback",
+  "decision",
+  "insight"
+]

AddedMay 1, 2026
Removedv0.2.8Apr 11, 2026
Changed5 schema fields changedv0.2.7Apr 6, 2026
- addedOutput schema / properties / page / default
```
Added value: +1
```
- addedOutput schema / properties / page_size / default
```
Added value: +0
```
- addedOutput schema / properties / total / default
```
Added value: +0
```
- addedOutput schema / properties / total_pages / default
```
Added value: +0
```
- removedOutput schema / required
```
Removed value: -[
-  "items",
-  "total",
-  "page",
-  "page_size",
-  "total_pages"
-]
```
First observedv0.2.4Apr 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior beyond that: result ordering (newest first) and that full content is returned rather than snippets. It says nothing about pagination limits or result volume, which would have been the last piece.

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 sentences, zero filler. Ordering and return format come first, and the intended use case is stated last in a single compact clause.

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?

An output schema exists, so return values need not be re-explained, and the description still helpfully characterizes them as full content. For a read-only list tool with annotations covering safety, the only real omission is pagination guidance for the otherwise-undocumented page/page_size parameters.

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 only 25%: tag and memory_type are documented in the schema, but page and page_size carry no descriptions. The description adds no parameter information at all — notably it never mentions that results are paginated or how page/page_size interact — so it fails to compensate for the documented coverage gap.

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 (browse/enumerate) and resource (memories), plus concrete scope details: ordered by creation date newest-first and full content rather than snippets. The phrase 'without a specific query' implicitly separates it from query-driven siblings like search_by_tag or recall_memory, though no sibling is named.

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

Usage Guidelines4/5

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

Gives a clear use case ('Use to enumerate or audit without a specific query'), which tells the agent when this tool is appropriate versus retrieval/search tools. It stops short of naming specific alternatives or explicit when-not conditions, so it falls just short of a 5.

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

Deploy Server