Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

group_search

Search for public groups or channels by topic on Telegram (or other channels). Returns matching groups with title, member count, and whether messages can be previewed.

Finds public groups/channels by topic — NOT individual people. To find or add a specific person by @username, use contacts.discover / contacts.find instead.

When to use:

  • Finding groups related to a topic or niche

  • Building a list of groups for outreach or monitoring

After searching, use group.scan to evaluate quality before joining.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-50, default 20)
channelYesChannel to search on (e.g. 'telegram')
keywordsYesSearch keywords or phrase (e.g. 'crypto trading signals'). A list of keywords is also accepted and joined with spaces.
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
  3. Removed
  4. Changed1 schema field changed
    • changedInput schema / properties / keywords / description
      Previous value: -"Search keywords or phrase (e.g. 'crypto trading signals')"New value: +"Search keywords or phrase (e.g. 'crypto trading signals'). A list of keywords is also accepted and joined with spaces."
  5. Added

TDQS

A4.1/5.0
Behavior3/5

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

The description adds real context beyond the annotation block: it describes the return payload ('title, member count, and whether messages can be previewed') and the follow-up workflow with group.scan. It does not cover auth/rate-limit or pagination behavior. Note the annotation block looks like uncustomized defaults (openWorldHint=false and idempotentHint=false are both questionable for a public Telegram search), so the read-only nature implied by 'Search' and the schema's 'Nothing is stored' sits awkwardly against readOnlyHint=false — but since the annotations are evidently unreliable defaults rather than an intentional counter-claim, this is not treated as a hard contradiction.

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 purpose and return shape, then a scannable 'When to use' block, and closes with the follow-up step. Slightly redundant between 'Search for public groups or channels by topic' and 'Finds public groups/channels by topic', but nothing is wasted overall.

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?

For a search tool with no output schema, it describes the returned fields and the recommended next action (group.scan), and clarifies the people-vs-group boundary. It omits any note on result ordering or pagination beyond the schema's limit, which is a minor gap.

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 the schema already documents all four parameters (limit, channel, keywords, in_workspace) including defaults and ranges. The description adds no parameter-level detail beyond what the schema provides, so the baseline of 3 applies.

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 with scope ('Search for public groups or channels by topic on Telegram'), and explicitly distinguishes itself from sibling tools by declaring it does NOT find individual people and pointing to contacts.discover/contacts.find for that. An agent can route correctly without opening either 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?

Provides an explicit 'When to use' list (finding groups by topic/niche, building outreach/monitoring lists), an explicit exclusion (not people → use contacts.discover/find), and a downstream step (use group.scan to evaluate before joining). Both the when and the alternative are named.

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