Skip to main content
Glama
mnemoverse

Mnemoverse Memory

by mnemoverse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

memory_invite_to_room

Invite someone to a room you own by minting a single-use invite code and a ready-to-forward message; set max uses or expiry to admit multiple people.

Instructions

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 when the user asks to invite someone to a room they own, including one just created with memory_create_room.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scopeNoRole the invitee gets — 'read' or 'read_write' (default read_write).
room_idYesThe room's id (room_...), from memory_create_room.
max_usesNoHow many people may join with this invite (default 1, single-use).
expires_in_daysNoDays until the invite expires (default 7).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeNoThe invite code (mnvr_...). Single-use by default, with a configurable use limit. Shown once.
scopeNoRole the invitee will get.
join_urlNoLanding URL the invitee can open to join.
expires_atNoISO 8601 expiry, or null.
room_addressNoThe room's domain address (xroom:<id>).
share_messageYesReady-to-forward invite text.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.11.0
    • changedInput schema / properties / max_uses / maximum
      Previous value: -9007199254740991New value: +1000
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "code": {
+      "description": "The invite code (mnvr_...). Single-use by default, with a configurable use limit. Shown once.",
+      "type": "string"
+    },
+    "expires_at": {
+      "description": "ISO 8601 expiry, or null.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "join_url": {
+      "description": "Landing URL the invitee can open to join.",
+      "type": "string"
+    },
+    "room_address": {
+      "description": "The room's domain address (xroom:<id>).",
+      "type": "string"
+    },
+    "scope": {
+      "description": "Role the invitee will get.",
+      "type": "string"
+    },
+    "share_message": {
+      "description": "Ready-to-forward invite text.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "share_message"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changedv0.10.2
    • addedInput schema / properties / max_uses
      Added value: +{
+  "description": "How many people may join with this invite (default 1, single-use).",
+  "maximum": 9007199254740991,
+  "minimum": 1,
+  "type": "integer"
+}
  3. Addedv0.5.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only carry the generic mutation profile (readOnlyHint=false, idempotentHint=false), so the description must add the real behavior — and it does: invites are single-use by default, max_uses lets one invite admit several people, and it explains the out-of-band delivery flow (user forwards the message, recipient either opens the link or dictates the code to their own assistant). That is exactly the kind of non-obvious semantics annotations cannot express.

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 core action is front-loaded in the first sentence, followed by invite lifetime semantics and then the routing condition. Four sentences, each carrying distinct information, with no filler.

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 small mutation tool with an output schema (so return shape needn't be described) and full schema coverage, the description supplies the missing pieces: the invite artifact, its default single-use behavior, and the human-in-the-loop forwarding step. Nothing an agent needs to invoke it correctly is absent.

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 schema already documents all four parameters, setting a baseline of 3. The description still adds meaning about max_uses by framing the default as 'single-use' and the override as letting 'several people join with the same one,' which clarifies intent rather than restating the field. scope and expires_in_days are left to the 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 and resource ('Mint an invite for a room you own') plus the concrete deliverable ('ready-to-forward message'), which separates it cleanly from memory_join_room and memory_create_room. An agent can pick this tool 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger condition ('Use when the user asks to invite someone to a room they own') and connects it to memory_create_room for the just-created-room case. It does not state when not to use it, e.g. that the recipient side belongs to memory_join_room, so it stops short of a full when/when-not/alternatives treatment.

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