Skip to main content
Glama

dialogbrain

by com.dialogbrain
OverviewDiscussionsAdmin

channels_list

Read-onlyIdempotent

📋 The messaging channels connected to this workspace and whether they are working.

One row per channel account: channel, display_name, status, error, and reconnect_url when the account needs repair. A channel in status 'error' is NOT receiving messages — say so plainly and give the person reconnect_url; it opens the repair directly, so do not tell them to look for it in settings and do not build a link of your own.

Pass only_broken=true to check for outages without listing the healthy channels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoOne account in detail, with its large_group_threshold (groups this large are left out of sync; change it with channels.sync_settings). For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels.
only_brokenNotrue = only the accounts that need attention (status 'error'). OMIT to list every channel of the workspace.
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
    • changedInput schema / properties / account_id / description
      Previous value: -"One account in detail. For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels."New value: +"One account in detail, with its large_group_threshold (groups this large are left out of sync; change it with channels.sync_settings). For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels."
  2. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
+  "description": "One account in detail. For a custom channel this adds whether it is listening or polling, why inbound is down, how many contacts it has, the progress of a history import, a health check and the agents that would answer on it. OMIT to list the workspace's channels.",
+  "type": "integer"
+}
  3. 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"
+}
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real behavioral context: the row-per-account shape, the meaning of status 'error' (NOT receiving messages), and a directive on how to hand the user reconnect_url rather than improvising a link. It omits pagination or result-size behavior, so not a full 5.

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?

Three short paragraphs, each front-loaded with its key point: what the list contains, how to interpret error rows and reconnect_url, then the outage-check shortcut. No filler sentences.

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?

There is no output schema, so the description carries the burden of describing returns, and it does — channel, display_name, status, error, reconnect_url, plus the extra detail returned when account_id is supplied. An agent has everything needed to call and interpret this tool.

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 all three parameters are already documented, including only_broken and account_id. The description restates only_broken's semantics and adds a use-case rationale but no syntax or format detail beyond the schema — the baseline 3 for high coverage.

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 (list) and resource (messaging channels connected to the workspace) plus the operational qualifier 'whether they are working'. This clearly separates it from siblings such as channels_connect, channels_sync_settings, and channels_get_profile.

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 an explicit conditional usage rule — 'Pass only_broken=true to check for outages without listing the healthy channels' — which tells the agent when to switch modes. It does not name a sibling alternative or state exclusions, so it falls just short of a 5.

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