Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

channels_reconnect

🔌 Bring a disconnected account back on its own, when the channel allows it.

Use it when channels.list shows an account as not connected / needs_reauth, or a send answers that the account is offline. A LinkedIn or Discord account connected through a browser login takes the session that login holds now (nothing is opened or typed on the site; the session must belong to the same member). When it cannot (no session in the browser, the same dead session, another channel), the answer says what a person has to do. Needs the member, admin or owner role.

Input Schema

NameRequiredDescriptionDefault
page_idNoDiscord only: a browser.open page of this workspace that is signed in to Discord as this account. The token is read from that open page (a sign-in made with browser.open is not saved to the account's browser identity). It must be the same Discord user.
account_idYesThe connected account (from channels.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 / page_id
      Added value: +{
+  "description": "Discord only: a browser.open page of this workspace that is signed in to Discord as this account. The token is read from that open page (a sign-in made with browser.open is not saved to the account's browser identity). It must be the same Discord user.",
+  "type": "string"
+}
  2. Added

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond annotations: for LinkedIn/Discord it reuses the current browser-login session without opening or typing on the site, requires the session to belong to the same member, and explains that failures return instructions for a person. This covers side effects and auth requirements that the non-readonly, non-destructive hints alone do not convey.

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?

Triggers are front-loaded in the second sentence and the whole text is three sentences with no filler. The LinkedIn/Discord clause is dense but still earns its place by explaining the session semantics.

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?

No output schema exists, and the description partly compensates by saying failures return what a person must do. For a non-destructive reconnect action with full param docs, that is nearly complete, though the success return value is left implicit.

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 coverage is 100%, so page_id, account_id and in_workspace are already fully documented. The description reinforces the browser-session context relevant to page_id but adds no syntax or format details beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: bringing a disconnected account back online, with the qualifier that the channel must allow it. It implicitly separates itself from channels_connect by describing a recovery of an existing account, but never names that sibling explicitly.

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?

Gives explicit trigger conditions: channels.list shows not connected / needs_reauth, or a send reports the account offline. It also states the fallback path when reconnection is impossible (no browser session, dead session, different channel) and the required role.

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