Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

channels_connect

🔌 Connect a messaging channel to this workspace, or find out how.

Call with no channel for the catalogue: every channel, its connect_mode and its link. Call with channel only to learn what to ask the person for (credential_fields). Call with channel + credentials to connect a credentials channel: email over IMAP with an app password, telegram_bot with a bot token, line with the channel access token and channel secret, avito.

Channels that need a QR scan, a phone code or a browser sign-in (telegram, whatsapp, instagram, facebook, email (Google sign-in), youtube, tiktok, x, threads, linkedin, zalo, maxru, the voice carriers) cannot be connected from here: the tool answers success with needs_person=true and the link https://dialogbrain.com/connect/, which opens the connection dialog for that channel. Give the person that link; do not tell them to look for it in settings. A website widget is not connected here at all: use widgets.create.

Input Schema

NameRequiredDescriptionDefault
channelNoChannel id, e.g. 'email', 'telegram_bot', 'whatsapp'. Omit for the catalogue.
credentialsNoThe fields credential_fields asked for. Never echoed back.
display_nameNoName for the account in the channel list.
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

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations, the description discloses the non-obvious success-with-needs_person=true pattern for OAuth/QR channels and the exact link shape returned. It also documents what each mode returns (catalogue with connect_mode and link, credential_fields, connection result) despite there being no output schema, and notes credentials are never echoed back.

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

Conciseness4/5

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

The three modes are front-loaded and easy to scan, and the channel lists are informative rather than filler. It runs slightly long with a few redundant emphatic clauses ('do not tell them to look for it in settings'), which cost a point.

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 four-parameter, open-world, non-idempotent tool with no output schema, the description covers every decision path: catalogue, field discovery, credential connection, needs_person fallback, and the out-of-scope widget case. Nothing an agent needs to call it correctly or explain the result is missing.

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, but the description adds genuine meaning by explaining the mode semantics of each parameter combination (channel omitted, channel alone, channel plus credentials) and what credentials must contain. The in_workspace parameter's scoping behavior is left entirely 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?

The description states a specific verb and resource ('connect a messaging channel to this workspace') and immediately enumerates three distinct call modes. It distinguishes itself from siblings by naming channels_connect_telegram_bot's domain implicitly (telegram_bot is listed as a credentials channel) and explicitly routing website widgets to widgets.create.

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?

It gives explicit when-to-use rules keyed to argument combinations ('Call with no channel for the catalogue', 'Call with channel only to learn what to ask', 'Call with channel + credentials to connect'). It also names the exclusion set (QR/phone-code/browser sign-in channels) and prescribes the correct follow-up action (give the person the link, use widgets.create for widgets).

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