Skip to main content
Glama
Sign In

Lemma Telepath

by company.lemma
OverviewDiscussionsAdmin

List Telegram chats

telegram_list_chats
Read-onlyIdempotent

Use this to browse the user's Telegram chats available in Telepath, including private chats, groups and channels, with archive or Session coverage disclosed in the result. Returns chat_id, display name, username, message count and last message time, not message contents. Default 20 chats; archive maximum 200, Session maximum 50. Connected channel inbox archives can supplement Session results; read effective_limit, session_limit, source, coverage and partial. This is a bounded list, not a total chat count. There is no pagination: repeating the same call does not advance. A full page may omit other chats. chat_type filters private chats, groups or channels; group includes supergroups. Session type filtering examines up to 1000 recent account dialogs, not the entire account. Null counts or dates mean unknown, not zero or no activity. Archive counts/dates describe saved/imported messages only. An empty filtered result means no matches in this source coverage, not that the account has no chats. Follow empty_reason and returned setup_required/history_notice; do not infer a lost connection or reconnect a working Session from an empty list. Operational errors are not empty results. For a named person, group or channel use telegram_find_chat; for a catch-up across chats use telegram_recent_messages. This is not a directory of all Telegram users or chats.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many chats to return. Default 20; archive maximum 200, Session maximum 50. Repeating a call does not fetch a next page.
chat_typeNoFilter by chat type. group includes basic groups and supergroups; channel means broadcast channels.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / limit / description
      Previous value: -"How many chats to return. Default 20."New value: +"How many chats to return. Default 20; archive maximum 200, Session maximum 50. Repeating a call does not fetch a next page."
  2. Changed1 schema field changed
    • addedInput schema / properties / chat_type
      Added value: +{
+  "description": "Filter by chat type. group includes basic groups and supergroups; channel means broadcast channels.",
+  "enum": [
+    "private",
+    "group",
+    "supergroup",
+    "channel",
+    "channel_dm"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the bounded-list behavior, per-source limits (archive 200, Session 50), no-pagination semantics, null meaning, archive-only counts, and how to interpret empty results via empty_reason/setup_required/history_notice. It also clarifies that operational errors are not empty results, which prevents a harmful reconnect inference.

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?

The description is front-loaded with purpose, then return fields, then limits, then interpretation guidance, and most sentences carry distinct operational value. It is dense and long with several run-on clauses, but little is redundant given the number of edge cases it must preempt.

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 two-parameter list tool with no output schema, the description names the returned fields, the coverage metadata to inspect, limit behavior per source, and empty-result interpretation. An agent has everything needed to call it and interpret the result without guessing about pagination or missing chats.

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 both limit and chat_type are already documented in the schema, including the group-includes-supergroups note and the no-next-page warning. The description reinforces the limit ceilings and filter meaning but adds little syntactic or semantic detail beyond the schema, so the baseline 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?

The description states a specific verb and resource (browse the user's Telegram chats) and immediately scopes the contents (private chats, groups, channels) with what is returned. It explicitly distinguishes itself from the closest siblings, telegram_find_chat and telegram_recent_messages, and clarifies it is not a user directory.

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?

It gives explicit routing: use telegram_find_chat for a named person/group/channel and telegram_recent_messages for catch-up across chats, and it names the case this tool is not for. It also warns that repeating the call does not page, so an agent knows not to loop for more results.

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

All Lemma Telepath 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