Mnemoverse Memory

memory_list_recent

Read-onlyIdempotent

List recent memories without a search query, using since and cursor to catch up after a break or page through older entries. Pass a room domain to review shared-room activity.

Instructions

List the NEWEST memories first — no search query needed. Semantic search answers 'what do I know about X'; this answers 'what happened lately': resuming work after a break, catching up on a shared room ('any new messages?'), or reviewing what was saved recently. Pass since (your last-seen time) to get only what's new, and page through older entries with the returned cursor. Complete by construction WITHIN ONE SCOPE — nothing is skipped there, unlike a semantic search. A page is also bounded by SIZE, so a page of long entries comes back shorter than limit and hands you a cursor for the rest — nothing is dropped, and following the cursor is how you get it. To catch up on a shared room you MUST pass its address as domain: rooms are separate stores and an unscoped call never covers them, though it names the ones you have (rooms_not_searched).

Input Schema

Name	Required	Description
`limit`	No	Most entries per page (default: 20). Newest first. ⚠️ A CEILING, not a promise: the page is ALSO bounded by size, so a page of long entries stops early and returns a cursor for the rest. In rooms whose entries run long, ask for 5–10 — a large `limit` there buys nothing the size budget will not take back, and costs round trips.
`since`	No	Only entries created at/after this ISO-8601 instant (naive = UTC) — your novelty watermark.
`until`	No	Only entries created at/before this ISO-8601 instant (inclusive). Pair with `since` to read a closed window — 'what happened on Monday' — instead of paging back from now.
`cursor`	No	Opaque cursor from a previous page's 'More older entries exist' line — continues the listing without skips or duplicates.
`domain`	No	Restrict to one domain. REQUIRED to read a shared room — pass its address ('xroom:room_01ABC'), because rooms are separate stores that an unscoped feed does NOT cover. Omit only when you mean your own domains. Room addresses come from memory_list_rooms. Room entries are often long — a room feed usually reaches its size budget after a handful of them, so expect to page (see `limit`).
`exclude_author`	No	Drop entries written by this author PRINCIPAL. ⚠️ NOT USABLE FROM HERE YET — the principal is never shown in these results, so there is no value you can get through this tool; a guess like 'me' filters nothing, silently. Same caveat as on memory_read.

Output Schema

Name	Required	Description
`items`	Yes	Entries newest-first (creation time descending).
`next_cursor`	No	Pass back as cursor for the next (older) page; null = listing complete. Absent when the service sent a continuation token this client will not pass on; the text then says the token could not be displayed.
`rooms_not_searched`	No	Present only on a call WITHOUT `domain`, when you have shared rooms or they could not be checked: rooms are separate stores that call did not search.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.16.0Oct 24, 2026

addedOutput schema / properties / rooms_not_searched

Added value: +{
+  "additionalProperties": false,
+  "description": "Present only on a call WITHOUT `domain`, when you have shared rooms or they could not be checked: rooms are separate stores that call did not search.",
+  "properties": {
+    "note": {
+      "description": "The same disclosure the text ends with.",
+      "type": "string"
+    },
+    "rooms": {
+      "description": "The live rooms this call did not search; present only when state is 'live'. A row missing room_id, address or role is omitted here and still named in `note`.",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "address": {
+            "description": "Domain address (xroom:<id>); pass as `domain` on read/write.",
+            "type": "string"
+          },
+          "archived": {
+            "description": "True if archived (owned rooms only).",
+            "type": "boolean"
+          },
+          "name": {
+            "description": "The room name.",
+            "type": "string"
+          },
+          "role": {
+            "description": "'owner' or 'member'.",
+            "type": "string"
+          },
+          "room_id": {
+            "description": "The room's id (room_...).",
+            "type": "string"
+          },
+          "scope": {
+            "description": "'read' or 'read_write'.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "room_id",
+          "address",
+          "role",
+          "archived"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "state": {
+      "description": "'live': the rooms listed can be read by passing an address as `domain`. 'archived-only': every room you have is archived and refuses reads. 'unknown': the room list could not be checked, so whether any room went unsearched is not known.",
+      "enum": [
+        "live",
+        "archived-only",
+        "unknown"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "state",
+    "note"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.15.3Oct 18, 2026

removedInput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

removedOutput schema / $schema

Removed value: -"http://json-schema.org/draft-07/schema#"

Changed1 schema field changedv0.11.0Sep 23, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "description": "Entries newest-first (creation time descending).",
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "author": {
+            "description": "Sanitized AGENT identity of the writer (never the human principal) — attribution in shared rooms.",
+            "type": "string"
+          },
+          "content": {
+            "description": "Stored memory content.",
+            "type": "string"
+          },
+          "created_at": {
+            "description": "UTC creation instant, ISO-8601; absent on legacy memories without a timestamp.",
+            "type": "string"
+          },
+          "domain": {
+            "description": "User-defined memory namespace or domain.",
+            "type": "string"
+          },
+          "memory_id": {
+            "description": "Identifier needed to rate or manage this saved memory.",
+            "type": "string"
+          }
+        },
+        "required": [
+          "memory_id",
+          "content",
+          "domain"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "next_cursor": {
+      "description": "Pass back as cursor for the next (older) page; null = listing complete. Absent when the service sent a continuation token this client will not pass on; the text then says the token could not be displayed.",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "items"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.10.0Sep 16, 2026

changedInput schema / properties / domain / description

Previous value: -"Restrict to one domain. REQUIRED to read a shared room — pass its address ('xroom:room_01ABC'), because rooms are separate stores that an unscoped feed does NOT cover. Omit only when you mean your own domains. Room addresses come from memory_list_rooms."New value: +"Restrict to one domain. REQUIRED to read a shared room — pass its address ('xroom:room_01ABC'), because rooms are separate stores that an unscoped feed does NOT cover. Omit only when you mean your own domains. Room addresses come from memory_list_rooms. Room entries are often long — a room feed usually reaches its size budget after a handful of them, so expect to page (see `limit`)."

changedInput schema / properties / limit / description

Previous value: -"Page size (default: 20). Newest first."New value: +"Most entries per page (default: 20). Newest first. ⚠️ A CEILING, not a promise: the page is ALSO bounded by size, so a page of long entries stops early and returns a cursor for the rest. In rooms whose entries run long, ask for 5–10 — a large `limit` there buys nothing the size budget will not take back, and costs round trips."

Changed3 schema fields changedv0.8.1Aug 10, 2026

changedInput schema / properties / domain / description

Previous value: -"Restrict to one domain (e.g. a shared room address 'xroom:...'); omit for all your domains."New value: +"Restrict to one domain. REQUIRED to read a shared room — pass its address ('xroom:room_01ABC'), because rooms are separate stores that an unscoped feed does NOT cover. Omit only when you mean your own domains. Room addresses come from memory_list_rooms."

addedInput schema / properties / exclude_author

Added value: +{
+  "description": "Drop entries written by this author PRINCIPAL. ⚠️ NOT USABLE FROM HERE YET — the principal is never shown in these results, so there is no value you can get through this tool; a guess like 'me' filters nothing, silently. Same caveat as on memory_read.",
+  "maxLength": 200,
+  "type": "string"
+}

addedInput schema / properties / until

Added value: +{
+  "description": "Only entries created at/before this ISO-8601 instant (inclusive). Pair with `since` to read a closed window — 'what happened on Monday' — instead of paging back from now.",
+  "type": "string"
+}

Addedv0.7.0Aug 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real behavioral context beyond them: completeness-within-a-scope, the size budget that can truncate a page below `limit`, the guarantee of no skips/duplicates across pages, and the `rooms_not_searched` signal on unscoped calls. It also discloses a limitation not visible elsewhere ('nothing is skipped there, unlike a semantic search').

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?

The opening sentence is well front-loaded and the paragraph advances from purpose to paging to scope. However, the size-budget/cursor mechanic is explained twice (once in prose, again in the `limit` description) and the paragraph is dense enough to be mildly repetitive.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 optional parameters and an output schema present, the description supplies exactly what the schema cannot: which scope the call covers, why a page may be short, how to continue, and where the room-address list comes from. An agent has everything needed to call it correctly on the first try.

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 description adds synthesis the schema cannot: `since` as a novelty watermark, `domain` as mandatory for room access, and the interaction between `limit` and the size budget that makes large limits wasteful in rooms. It largely restates the schema's per-parameter caveats rather than adding new semantics, which keeps it below 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 description leads with a specific verb and ordering ('List the NEWEST memories first') and immediately contrasts itself with the sibling capability of semantic search ('what happened lately' vs 'what do I know about X'). An agent can pick between this and memory_read 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?

It names concrete use cases (resuming after a break, catching up on a room, reviewing recent saves), states when to pass `since` versus paging with the cursor, and gives an explicit MUST for the alternative store ('to catch up on a shared room you MUST pass its address as `domain`'). When-not guidance is present: unscoped calls never cover rooms.

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

Deploy Server