Skip to main content
Glama

dialogbrain

by io.github.saloprj
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. 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
    • 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"
+}
  2. 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"
+}
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only/idempotent/non-destructive, yet the description adds substantial behavioral context beyond them: exactly what each row contains, that status 'error' means the channel is NOT receiving messages, and that reconnect_url opens repair directly so the agent must not fabricate its own link. This is precisely the kind of guidance annotations cannot express.

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?

Two short paragraphs, front-loaded with the resource and then the actionable error-case instructions. Every sentence carries weight; nothing is redundant or decorative beyond the leading emoji.

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 three-param read tool with full schema coverage, the definition covers output columns, error semantics, remediation behavior, and the filtering option. No output schema is needed because the return shape is described inline.

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. The description reframes only_broken as an outage-checking use case rather than a bare filter flag, which adds a little meaning beyond the mechanical schema text, though account_id and in_workspace are 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?

States a specific verb and resource ('list the messaging channels connected to this workspace') plus the health status dimension. An agent can distinguish it from channels_connect, channels_get_profile, and channels_contacts without opening the schema, and the row layout is spelled out.

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 a clear condition for the only_broken path ('to check for outages without listing the healthy channels') and clear operational guidance for the error case. It does not name an alternative sibling to use instead, so it stops just short of fully explicit routing.

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