Skip to main content
Glama
mnemoverse

Mnemoverse Memory

by mnemoverse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_list_rooms

Read-onlyIdempotent

List owned and joined shared memory rooms with domain addresses for reads and writes, so you can re-find and resume rooms in new sessions.

Instructions

List the shared memory rooms you can use — the ones you OWN plus the ones you've JOINED — each with the address to pass as domain on memory_read, and on memory_write too where your membership scope is read_write; a read-only membership has that write refused. Use this to RE-FIND a room in a new session (e.g. 'what rooms do I have?', 'resume the room with my teammate') instead of having to create or re-join it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
roomsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.12.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "rooms": {
+      "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"
+    }
+  },
+  "required": [
+    "rooms"
+  ],
+  "type": "object"
+}
  2. Addedv0.7.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: which rooms are returned, that the returned address feeds the `domain` argument on memory_read/memory_write, and that read-only membership causes writes to be refused. Return value shaping isn't described, but the key membership caveat is.

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?

One dense sentence that front-loads the core scope (owned + joined) and then the usage rationale. Every clause earns its place, though the em-dash interjection about read_write scope makes it slightly heavy for a list tool.

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?

An output schema exists, so return-format explanation is not required, yet the description still conveys the practically important bit of the output (the address for use as `domain`). For a zero-param, read-only list tool, nothing an agent needs is missing.

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?

The tool takes zero parameters, so the baseline is 4. The description's mention of the `domain` address is output-to-other-tools mapping rather than input semantics, but it adds useful cross-tool meaning without overloading the empty schema.

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+resource (list shared memory rooms) and immediately scopes it to the two membership sources (OWNED + JOINED). Clearly differentiates from siblings like memory_create_room and memory_join_room by framing this as the discovery operation.

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 says when to use it ('RE-FIND a room in a new session') and when not to (instead of having to create or re-join it), giving concrete trigger phrasings. The alternative tools are implied by name and purpose.

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

Deploy Server

Other Tools