Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

group_create

Create a new group on a channel: a Telegram group, a WhatsApp group, or a Discord SERVER (a community with text channels inside; Discord calls it a guild) owned by the connected account. Returns the new group's chat ID and invite link.

What this does:

  • Creates a new group with the specified title

  • Returns chat_id, invite_link, and channel_ref for further operations

  • Optionally registers the group in your inbox for monitoring

  • Discord: also makes the text channels asked for (beside #general) and one permanent invite link; chat_id is the server id, channel_ref the #general thread, channels lists every text channel with its thread_ref (messages.send posts into one). People cannot be added to a server: send them invite_link. A step Discord refused after the server was made (a channel, the invite) is in problems; the server exists. Nothing is hosted by DialogBrain: the server lives at Discord.

Returns: success, chat_id, channel_ref, title, thread_id, invite_link.

Input Schema

NameRequiredDescriptionDefault
aboutNoOptional description or about text for the group
titleYesTitle/name of the group to create
channelYesChannel to create the group on: 'telegram', 'whatsapp' or 'discord' (a server)
channelsNoDiscord only: text channels to create inside the new server, beside its default #general, e.g. ["rules", "announcements", "submissions"], or objects {"name", "topic"}; at most 10 (more are added in Discord itself). Refused on channels whose groups have no rooms inside (Telegram, WhatsApp).
account_idNoWhich of the workspace's accounts on this channel creates the group (from channels.list). OMIT with one account; with several the workspace's own account is preferred over a shared one.
group_typeNoType of group to create. Options: 'supergroup' (default), 'basic'. Telegram-only; ignored on WhatsApp.supergroup
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
participantsNoPeople to put in the group at creation: phone numbers or JIDs on WhatsApp, @usernames or phone numbers on Telegram. Without this the group is created empty and the creator is its only member, which on WhatsApp means nobody can be shown it — there is no invite link to send. Reported back per person in `participants_added` and `participants_failed`.
register_in_inboxNoAuto-register the created group in your inbox for monitoring. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "Which of the workspace's accounts on this channel creates the group (from channels.list). OMIT with one account; with several the workspace's own account is preferred over a shared one.",
+  "type": "integer"
+}
    • changedInput schema / properties / channel / description
      Previous value: -"Channel to create the group on (e.g., 'telegram', 'whatsapp')"New value: +"Channel to create the group on: 'telegram', 'whatsapp' or 'discord' (a server)"
    • addedInput schema / properties / channels
      Added value: +{
+  "description": "Discord only: text channels to create inside the new server, beside its default #general, e.g. [\"rules\", \"announcements\", \"submissions\"], or objects {\"name\", \"topic\"}; at most 10 (more are added in Discord itself). Refused on channels whose groups have no rooms inside (Telegram, WhatsApp).",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  3. Added
  4. Removed
  5. Added

TDQS

A4.3/5.0
Behavior4/5

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

Discloses behavior beyond the annotations: partial-success semantics on Discord ('a step Discord refused after the server was made ... is in problems; the server exists'), the empty-group caveat, the inbox-registration side effect, and the explicit ownership statement that DialogBrain hosts nothing. It omits permission/auth prerequisites and rate limits, which matter because idempotentHint=false means a retry can create a second group.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the key scoping sentence, but the 'What this does' bullet list largely repeats what the schema already documents (channels max 10, participants behavior), and the Discord paragraph is dense with backticked field names. Roughly a third of the text could be cut without losing information an agent lacks.

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?

Nine parameters, three divergent backends, and no output schema — yet the description covers creation, per-channel divergence, failure reporting, return fields, and the invite-link escape hatch. An agent can call this correctly and interpret a partial-failure response without further information.

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 earns an extra point by interpreting parameter effects rather than restating them — e.g. chat_id is the server id and channel_ref the #general thread for Discord, extra channels beyond 10 are added in Discord itself, and channels is refused on Telegram/WhatsApp. It still doesn't explain the channel_ref/thread_ref mechanics outside the Discord branch.

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 new group on a channel') and immediately disambiguates the three backends, including the non-obvious fact that a Discord 'group' is a SERVER/guild. It also predicts the return values (chat_id, invite_link), so an agent knows what it gets without opening a 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 clear situational guidance: Discord servers cannot have people added, so send invite_link instead; without participants the group is empty and unshareable on WhatsApp. It does not explicitly route the agent among siblings like group_join, group_add_member, or group_list, so the when-not-to-use case is left implicit.

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

All dialogbrain toolsInspect
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.

Resources