Skip to main content
Glama
Sign In
tg-agent

tg-agent

by Creatfire
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List dialogs

tg_list_dialogs
Read-only

List Telegram channels, groups, and private chats an account has joined, including private channels. Filter by kind or query and control fields, limit, and format for compact context.

Instructions

List the channels, groups and private chats the account has joined (including private channels).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tg_list_dialogs"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoall
limitNo
queryNoFilter by title or username
fieldsNoKeep only these fields in list items (e.g. ["message_id","name","size"])
formatNocompact = lists as {columns, rows} tables; saves a lot of context for long listingsjson
accountNoAccount id (see tg_list_accounts). Defaults to the default account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one meaningful behavioral fact — only joined dialogs are returned, private channels included — but says nothing about result shape, ordering, or what happens when limit is hit.

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?

A single well-formed sentence with the scope constraint front-loaded and zero filler. It is efficient, but its brevity comes partly from omitting guidance rather than from tightening a complete statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter listing tool with no output schema, the description says nothing about what a returned dialog looks like, how pagination or limit behaves, or when the compact format is preferable. Annotations cover safety, but the operational information an agent needs to call this well is largely absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 67%, and two important parameters (kind and limit) carry no description in the schema. The description does not compensate: it never mentions the kind filter, the limit/cap behavior, or that an account can be selected, so the enum values channels/groups/users and the 100/500 bounds are left unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ("List") and an explicit resource scope: channels, groups and private chats the account has joined, with a clarifying parenthetical about private channels. That is enough to distinguish it from a message search or a file listing, though it does not name a sibling tool directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance at all — no statement of when to prefer this over tg_search_messages, tg_resolve_chat or tg_compare_chats, and no mention of prerequisites or follow-up steps. The reader must infer the role of this tool from the description alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools