Mnemoverse Memory

memory_list_rooms

Read-onlyIdempotent

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 Olya') instead of having to create or re-join it.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`rooms`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / rooms / items / required

Previous value: -[
-  "room_id",
-  "name",
-  "address",
-  "role",
-  "scope",
-  "archived"
-]New value: +[
+  "room_id",
+  "address",
+  "role",
+  "archived"
+]

First observedSep 22, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds meaningful behavioral context by explaining that returned addresses are suitable for memory_read and conditionally for memory_write, including that read-only membership will have writes refused. This goes beyond the annotation hints and provides practical behavioral expectations.

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?

The description is two sentences, but each clause carries essential information: ownership/joined scope, how returned addresses are used, the read-only write caveat, and concrete usage examples. There is no filler or redundancy.

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?

For a zero-parameter tool with an output schema present, the description is complete. It explains what the tool lists, how the results should be consumed, and when to invoke it across sessions. It also implicitly clarifies membership semantics, so an agent has enough context to call and interpret the tool correctly.

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 has zero parameters, so the input schema fully documents everything. The description adds no parameter information, which is appropriate and unnecessary here. A baseline of 4 is appropriate for a parameterless tool with complete schema coverage.

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 states a clear, specific action: listing the shared memory rooms the user owns plus those they've joined. It also explains that each result includes the address to pass as `domain` on memory_read and memory_write, which distinguishes this tool from sibling list tools like memory_list_recent or memory_graph.

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?

The description explicitly says to use this tool to re-find a room in a new session, giving concrete examples like 'what rooms do I have?' and 'resume the room with Olya'. It also contrasts it with creating or re-joining a room, making the intended use case and alternatives clear.

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

All Mnemoverse Memory tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.