Skip to main content
Glama
Sign In

DialogBrain

by com.dialogbrain.api
OverviewDiscussionsAdmin

group_list

Read-onlyIdempotent

List groups in this workspace's DISCOVERY/SCORING list (the discovered_group table).

⚠️ This is NOT your messageable inbox. It is a subset used for discovery + quality scoring. Absence here does NOT mean a chat isn't joined or can't be messaged. Each row includes thread_channel_ref — the ref a synced thread carries — so you can match rows against search_threads results. To get a thread_id you can send to, use search_threads.

Lifecycle values:

  • discovered: found but not yet evaluated

  • bookmarked: saved for later

  • monitored: joined and actively syncing messages

  • dismissed: hidden

By default, dismissed groups are excluded. Returns: id, title, member_count, lifecycle, scan_status, overall_score, is_member, can_post, my_rank.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results (1-100, default 20)
offsetNoPagination offset. OMIT to start at row 0 (default).
channelNoFilter by channel (e.g. 'telegram'). Optional.
lifecycleNoFilter by state: discovered, bookmarked, monitored (=joined/syncing), dismissed. OMIT to include all states (dismissed excluded by default elsewhere).
min_scoreNoMinimum overall score (0.0-1.0). Optional.
account_idNoOnly groups of this account (from channels.list). OMIT to list groups of every account.
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": "Only groups of this account (from channels.list). OMIT to list groups of every account.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, but the description adds non-obvious behavior: dismissed groups are excluded by default, the lifecycle states and their meanings, and that thread_channel_ref is the join key against search_threads results. It stops short of saying how rows are ordered or how pagination interacts with the default filter, which matters for a limit/offset list tool.

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?

Front-loads the identity warning before any mechanics, then the join-key hint, then a scannable lifecycle list and a returns line. Efficient overall, though the returns enumeration is a long single line whose value is mostly in the absence of an output schema.

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 7-parameter, all-optional, read-only list tool with no output schema, the description covers scope, defaults, filter semantics, the returned field set, and the cross-tool join key. Nothing an agent needs in order to call it correctly or interpret results 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 coverage is 100%, so the baseline is 3. The lifecycle value glossary (discovered/bookmarked/monitored/dismissed) does add meaning beyond the bare enum, and the default-exclusion note ties to that filter, but the other six parameters (limit, offset, channel, min_score, account_id, in_workspace) get nothing beyond their schema text.

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 groups") and immediately scopes it to the DISCOVERY/SCORING list backed by the discovered_group table. It explicitly contrasts itself with the messageable inbox and with search_threads, so an agent can distinguish it from group_search, contacts_groups, and search_threads 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?

Gives an explicit when-not ("This is NOT your messageable inbox") plus the consequence of misreading it ("Absence here does NOT mean a chat isn't joined or can't be messaged"), and names the alternative tool for the other job ("To get a thread_id you can send to, use search_threads"). This is exactly the routing guidance an agent needs.

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