Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

group_preview_messages

Read-onlyIdempotent

Read recent public messages from a group without joining it. Only works for groups where can_preview_history=true.

Use this to manually evaluate message quality before deciding to join. For an automated quality score, use group.scan instead.

Returns: list of recent messages with sender identity (username, name, admin flag), text (150-char previews; pass full_text=true for untruncated), date, is_reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of recent messages to fetch (1-100, default 20)
group_idYesGroup to act on. Accepts either the discovered-group id from group.search / group.list, or the platform's own group id (e.g. a Telegram chat id like -1001234567890).
full_textNoReturn untruncated message text. OMIT for 150-char previews (keeps large batches consumable).
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
    • addedInput schema / properties / full_text
      Added value: +{
+  "description": "Return untruncated message text. OMIT for 150-char previews (keeps large batches consumable).",
+  "type": "boolean"
+}
  5. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare the read-only, idempotent, non-destructive safety profile, so the bar is lower. The description adds real behavioral context beyond that: the can_preview_history=true gating precondition and the 150-char preview default with full_text override.

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?

Front-loaded purpose, then usage, then return shape, each in a distinct sentence or section. Every sentence adds information (scope, alternative, return format) with no filler.

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 read-only preview tool with no output schema, the description compensates by enumerating the return fields (sender identity, text, date, is_reply). Annotations cover safety, and the precondition and alternative are noted, so nothing essential is missing.

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%, giving a baseline of 3 (the schema documents all four params). The description goes further by explaining the truncation behavior of full_text ('150-char previews; pass full_text=true for untruncated'), adding semantic clarity on why the flag exists.

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 ('Read recent public messages from a group') plus a key scope constraint ('without joining it'). This clearly distinguishes it from siblings like group_join and group_scan.

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?

Explicitly says when to use it ('to manually evaluate message quality before deciding to join') and names the alternative for a different need ('For an automated quality score, use group.scan instead'). The precondition (can_preview_history=true) is also stated.

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