Mnemoverse Memory

memory_create_room

Creates a shared memory room that lets other people's assistants read and write context across Claude, ChatGPT, and Cursor. Returns the room address for memory writes and reads.

Instructions

Create a SHARED memory room — a space OTHER people's assistants can read, and write too when their invite granted read_write (the default scope), across Claude/ChatGPT/Cursor. Use when the user wants to share context or collaborate with someone else (e.g. 'make a room for me and my teammate'). Returns the room's address; pass that address as the domain on memory_write/memory_read to use it, and on memory_list_recent to catch up on what others added. People join through an invite minted with memory_invite_to_room.

Input Schema

Name	Required	Description	Default
`name`	Yes	Room name, unique within your account (e.g. 'launch-team').
`description`	No	Optional description of the room.

Output Schema

Name	Required	Description
`name`	No	The room name as stored.
`address`	Yes	Domain address (xroom:<id>); pass as `domain` on read/write.
`room_id`	Yes	The room's id (room_...); pass to memory_invite_to_room.

Schema Changelog

Changes observed during successful MCP inspections.

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.14.2Oct 1, 2026

changedInput schema / properties / name / description

Previous value: -"Room name, unique within your account (e.g. 'me-and-olya')."New value: +"Room name, unique within your account (e.g. 'launch-team')."

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": {
+    "address": {
+      "description": "Domain address (xroom:<id>); pass as `domain` on read/write.",
+      "type": "string"
+    },
+    "name": {
+      "description": "The room name as stored.",
+      "type": "string"
+    },
+    "room_id": {
+      "description": "The room's id (room_...); pass to memory_invite_to_room.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "room_id",
+    "address"
+  ],
+  "type": "object"
+}

Addedv0.5.0Jul 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=false), so the description only needs to add context — and it does: it discloses the shared/cross-platform nature, the default read_write invite scope, and what is returned. It stops short of stating error behavior (e.g. duplicate-name rejection) or any permission/rate constraints, but the added context is substantial.

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?

Three sentences, front-loaded with the core action and the usage trigger before the downstream instructions. The parentheticals (default scope, platform list, example phrase) are informative but make the middle slightly dense; nothing is redundant enough to remove outright.

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?

Although an output schema exists, the description still names the key return value (the room's address) and explains how to feed it into memory_write/memory_read/memory_list_recent, which is the critical integration knowledge an agent needs. Nothing required to invoke and then use the result is missing.

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 description coverage is 100%, so both parameters are already documented in the schema. The description's mention of `domain` refers to other tools' parameters, not this tool's inputs, so it adds no meaning to `name` or `description` beyond the schema. Baseline 3 applies.

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 and resource ('Create a SHARED memory room') and immediately qualifies the resource as a cross-assistant shared space, which cleanly separates it from siblings like memory_join_room and memory_list_rooms. An agent can identify the operation without opening the 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?

Gives an explicit trigger ('Use when the user wants to share context or collaborate with someone else') with a concrete example utterance, and routes the complementary action to the named sibling memory_invite_to_room. The condition that selects this tool over its alternatives is stated rather than implied.

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

Deploy Server