Skip to main content
Glama
dappros

Ethora MCP Server

by dappros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Chat Room

ethora-app-create-chat

Create a chat room in an app you own. Pin it to default rooms so new users auto-join, or leave unpinned for opt-in. Returns the new room object and JID.

Instructions

Create a new chat room (MUC room) inside an app the caller owns. Every room created this way is listed in the app's rooms (defaultRooms); pinned: true additionally makes new users auto-join it (existing users are not added), pinned: false (default) keeps it opt-in. Returns the new room object including its JID. Requires: a selected app (ethora-app-select) or an explicit appId. Auth: user-auth mode, active session; the caller must own the app. Errors: 401 not logged in; 403 not owner; 404 unknown appId; 422 invalid title.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
appIdNo24-char hex ObjectId of the app to create the chat room in. Optional — defaults to the app most recently passed to `ethora-app-select`.
titleYesDisplay name for the new chat room. Visible to all members; not required to be unique within the app.
pinnedNoIf `true`, the room is added to the app's default rooms list — every new user of the app auto-joins it. If `false`, the room exists but users must be added explicitly.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv26.9.3
    • changedInput schema / properties / appId / description
      Previous value: -"appId for app"New value: +"24-char hex ObjectId of the app to create the chat room in. Optional — defaults to the app most recently passed to `ethora-app-select`."
    • addedInput schema / properties / pinned / default
      Added value: +false
    • changedInput schema / properties / pinned / description
      Previous value: -"pinned for chat"New value: +"If `true`, the room is added to the app's default rooms list — every new user of the app auto-joins it. If `false`, the room exists but users must be added explicitly."
    • changedInput schema / properties / title / description
      Previous value: -"title for chat"New value: +"Display name for the new chat room. Visible to all members; not required to be unique within the app."
    • changedInput schema / required
      Previous value: -[
-  "appId",
-  "title",
-  "pinned"
-]New value: +[
+  "title"
+]
  2. First observedv1.0.0

TDQS

A4.7/5.0
Behavior5/5

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

The description goes well beyond the annotations by disclosing side effects: rooms are listed in `defaultRooms`, `pinned: true` auto-joins new users but not existing users, and the operation returns the new room object including JID. It also specifies auth requirements and error codes (401, 403, 404, 422).

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 well-structured: purpose first, then behavioral effects, then requirements, auth, and errors. Every sentence carries useful 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?

Even without an output schema, the description states the key return value (new room object including JID), covers all relevant error cases, and specifies prerequisites and ownership conditions. Nothing essential is missing for an agent to invoke this 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?

Schema coverage is 100%, so the schema already documents parameters well. The description adds valuable nuance, particularly that `pinned: true` does not add existing users and that `pinned: false` keeps the room opt-in, which enriches the pinned parameter semantics beyond 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?

The description clearly states a specific action and resource: 'Create a new chat room (MUC room) inside an app the caller owns.' It also explains the room's lifecycle effect ('listed in the app's rooms (`defaultRooms`)'), which distinguishes it from chat messaging or chat deletion tools.

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?

It gives explicit prerequisites: a selected app via `ethora-app-select` or an explicit `appId`, plus a clear distinction between `pinned: true` and `pinned: false` behavior. It does not explicitly name alternative tools or state when not to use this tool, so it falls just short of a 5.

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