Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

group_join

Join a group and start syncing its messages to your inbox. The group must be in your discovery list (use group.search or group.add first).

What this does:

  • Joins the group on Telegram (or other channel)

  • Creates a thread in your inbox for syncing messages

  • Optionally enables AI auto-reply drafts

Returns: success, thread_id, auto_reply_enabled.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup to act on. Accepts either the discovered-group id from group.search / group.list, or the platform's own group id (e.g. a Telegram chat id like -1001234567890).
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
enable_auto_replyNoEnable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: false (large public groups would otherwise generate drafts for every incoming message).

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Added
  3. Removed
  4. Changed2 schema fields changed
    • removedInput schema / properties / enable_auto_reply / default
      Removed value: -true
    • changedInput schema / properties / enable_auto_reply / description
      Previous value: -"Enable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: true."New value: +"Enable AI auto-reply drafts for messages in this group. Drafts can be reviewed and sent manually. Default: false (large public groups would otherwise generate drafts for every incoming message)."
  5. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent, non-open-world operation. The description adds real value beyond that by enumerating the side effects (joins on the platform, creates an inbox thread, may enable auto-reply drafts) and the returned fields. It does not say whether a repeat call creates a duplicate thread or whether joining is reversible, which is the remaining gap.

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?

Front-loaded one-line summary followed by a short bulleted side-effect list and a returns line — every element earns its place and nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly compensates by listing the return values (success, thread_id, auto_reply_enabled), and it covers prerequisites and side effects for a mutation tool. The only shortfall is not clarifying repeat-call/duplicate-thread behavior for a tool flagged non-idempotent.

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 description coverage is 100% and each parameter (group_id, in_workspace, enable_auto_reply) is already well documented in the schema, including the auto-reply default and rationale. The description's 'Optionally enables AI auto-reply drafts' merely restates enable_auto_reply, so the baseline 3 applies.

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 first sentence gives a specific verb ('Join') plus resource ('a group') and the immediate consequence ('start syncing its messages to your inbox'). The 'What this does' list further disambiguates it from siblings like group_add (which only adds to discovery), group_create, and group_leave.

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 states a clear prerequisite ('The group must be in your discovery list') and routes the agent to the right alternatives by name ('use group.search or group.add first'). What is missing is the inverse case — what happens if the group is already joined, or when NOT to call this — so it stops short of a full when/when-not rule set.

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