Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

group_add

Add a specific group to your discovery list by @username or invite link (t.me/...).

Groups and channels only — this does NOT add an individual person/contact. To add a person by @username (e.g. a customer or lead), use contacts.discover then contacts.sync instead.

When to use:

  • You already know the group's @username or invite link

  • Adding a known group without searching

Returns: group metadata including id, title, member_count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkYesThe group's @username or invite link (e.g. '@phuket' or 't.me/...')
channelYesChannel the group is on (e.g. 'telegram')
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

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. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly=false, idempotent=false, destructive=false, openWorld=false, so the safety/dedup profile is covered. The description still adds real behavioral context beyond them: the target is a 'discovery list' (not actual group membership), and it discloses the return shape. It stops short of permissions, rate limits, or side effects, keeping it at a 4.

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 with the core action and scoping clause before the usage bullets and return note; the disambiguation sentences and bulleted when-to-use each carry 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 non-idempotent mutation with no output schema, it covers purpose, exclusions, alternatives, usage triggers, and an inline description of returned fields (id, title, member_count). Nothing an agent needs to call it correctly is missing.

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%, so the schema already documents 'link', 'channel', and 'in_workspace'. The description restates the link format (@username or t.me/...) but adds no format detail or constraint the schema lacks, so the baseline 3 is appropriate.

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 ('Add a specific group to your discovery list') and immediately scopes it ('Groups and channels only'). It distinguishes itself from the many sibling group_* tools and from contacts_* by name, so an agent can route without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Provides an explicit 'When to use' section (known @username/invite link, adding without searching) and explicit exclusions ('does NOT add an individual person/contact'), plus the concrete alternative chain contacts.discover then contacts.sync for the person case.

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