Mnemoverse Memory

memory_invite_to_room

Mint an invite for a room you own and get a ready-to-forward message. An invite is single-use by default; pass max_uses to let several people join with the same one. The user sends that message to the person they want to add (any messenger); the recipient opens the link or tells THEIR assistant the code to join. Use after memory_create_room, or whenever the user says 'invite ' to an existing room.

Input Schema

TableJSON Schema

Name	Required	Description
`scope`	No	Role the invitee gets — 'read' or 'read_write' (default read_write).
`room_id`	Yes	The room's id (room_...), from memory_create_room.
`max_uses`	No	How many people may join with this invite (default 1, single-use).
`expires_in_days`	No	Days until the invite expires (default 7).

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No	The invite code (mnvr_...). Single-use by default, with a configurable use limit. Shown once.
`scope`	No	Role the invitee will get.
`join_url`	No	Landing URL the invitee can open to join.
`expires_at`	No	ISO 8601 expiry, or null.
`room_address`	No	The room's domain address (xroom:<id>).
`share_message`	Yes	Ready-to-forward invite text.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 25, 2026

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

changedInput schema / properties / expires_in_days / description

Previous value: -"Days until the invite expires (1-90, default 7)."New value: +"Days until the invite expires (default 7)."

changedInput schema / properties / max_uses / description

Previous value: -"How many accounts may redeem the invite (1-1000, default 1)."New value: +"How many people may join with this invite (default 1, single-use)."

changedInput schema / properties / room_id / maxLength
```
Previous value: -200New value: +100
```

changedInput schema / properties / scope / description

Previous value: -"Role the invitee gets: 'read' or 'read_write' (default read_write)."New value: +"Role the invitee gets — 'read' or 'read_write' (default read_write)."

changedOutput schema / required

Previous value: -[
-  "code",
-  "join_url",
-  "share_message",
-  "scope",
-  "room_address",
-  "expires_at"
-]New value: +[
+  "share_message"
+]

First observedSep 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With annotations carrying almost no behavioral detail, the description properly carries the burden: it explains the single-use default, the max_uses override, the fact that the user forwards a prepared message, and the recipient's two join paths (link or code). It does not cover error cases or rate limits, but it covers what an agent needs to invoke safely.

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 sentences front-load the core action and output, then provide workflow and trigger context. There is no filler; every sentence contributes distinct operational information.

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?

Given that all parameters are documented, an output schema exists, and annotations are present, the description supplies the missing context: ownership prerequisite, default single-use behavior, the forwarding flow, and when to invoke. An agent has enough to call this tool correctly without guessing.

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. The description adds meaning beyond the schema by explaining max_uses as 'let several people join with the same one' and room_id as requiring a room the user owns. It does not add extra semantics for scope or expires_in_days, but the schema already documents those clearly.

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 action ('Mint an invite') and resource ('for a room you own'), and immediately distinguishes it from sibling tools like memory_create_room and memory_join_room. It also names the concrete outcome, a ready-to-forward message, so an agent can tell exactly what this tool does.

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 explicitly says 'Use after memory_create_room' and maps a user trigger phrase ('invite <someone>') to this tool, which is strong routing guidance. It does not explicitly name when not to use it or point to an alternative, but the triggers given are specific and actionable.

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.