Mnemoverse Memory

memory_join_room

Idempotent

Join a shared memory room using an invite code (starts with 'mnvr_'). Use when the user pastes an invite code or says something like 'join room with code ...'. After joining, use the returned address as the domain on memory_read to read the shared room — the result tells you what you may do with it: memory_write to that address is only allowed when your membership scope is read_write; a read-only membership has that write refused; and when the server does not report a scope, whether memory_write would succeed is stated as unknown rather than promised either way.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`code`	Yes	The invite code (mnvr_...).

Output Schema

TableJSON Schema

Name	Required	Description
`name`	No	The room name.
`scope`	No	Your role in the room ('read' \| 'read_write').
`address`	Yes	Domain address (xroom:<id>); pass as `domain` on read/write.
`room_id`	Yes	The room's id (room_...).
`next_steps`	Yes	How to use the room now.
`already_member`	No	True if you were already a member (no-op join).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 25, 2026

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

changedOutput schema / required

Previous value: -[
-  "room_id",
-  "address",
-  "name",
-  "scope",
-  "already_member",
-  "next_steps"
-]New value: +[
+  "room_id",
+  "address",
+  "next_steps"
+]

First observedSep 22, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description explains the post-join behavior: the returned address should be used as the domain on memory_read, and whether memory_write succeeds depends on membership scope. It even handles the unknown-scope case instead of promising either outcome, which is valuable transparency.

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?

Three dense sentences, with the action and trigger front-loaded. The later permission/scope guidance earns its place because it directly affects how an agent should use the result. No filler is present.

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 only one required parameter, 100% schema coverage, and a provided output schema, the description still adds important context about what to do after joining and how memory_write authorization is determined. No essential calling information 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 coverage is 100% and the schema already says the code is 'The invite code (mnvr_...)'. The description repeats the 'mnvr_' prefix and adds user-trigger context, but provides little additional semantic meaning beyond what the schema already supplies.

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 specific verb ('Join') and resource ('shared memory room'), and immediately identifies the invite-code format ('mnvr_'). This cleanly distinguishes it from sibling tools like memory_create_room and memory_invite_to_room.

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?

The description gives explicit triggers: 'when the user pastes an invite code or says something like join room with code ...'. It does not spell out when-not-to-use or name alternative tools, but the trigger conditions are clear enough for confident selection.

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.