Skip to main content
Glama
Sign In
kotlogramme

kotlogramme

by J0s3f
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

List chats

telegram_list_chats
Read-onlyIdempotent

Lists your Telegram private chats, groups, and channels by recent activity, returning IDs, titles, usernames, unread counts, and last-message previews for selecting a chat or paging through results.

Instructions

Lists the account's chats (private chats, groups, channels), most recently active first, with id, title, @username, unread count and a preview of the last message. The id is what the other tools take as 'chat'. When the page is full the result has 'next_cursor'; pass it back as 'cursor' for more.

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": "telegram_list_chats"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many chats to return.
cursorNoThe 'next_cursor' of the previous page, to continue after it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.11.1

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the safety profile is covered. The description adds value beyond that: result ordering (most recently active first), the exact payload fields, the pagination contract, and the note that the returned id is what other tools accept as 'chat' — a genuinely useful cross-tool detail.

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?

Three dense sentences with no filler; the resource and scope come first, then the return shape, then pagination. Every sentence carries information an agent needs.

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?

With no output schema, the description carries the burden of describing return values and does so (id, title, @username, unread count, last-message preview) plus pagination behavior. For a two-parameter read tool, nothing material 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 description coverage is 100%, so the baseline is 3. The description still adds meaning by explaining the round-trip relationship between the returned 'next_cursor' and the 'cursor' parameter, which the schema alone only hints at.

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 ('Lists the account's chats') and enumerates the subtypes covered (private chats, groups, channels), which separates it from siblings like telegram_list_contacts or telegram_list_folders. It also specifies ordering and the fields returned, so an agent knows exactly what it gets.

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

Usage Guidelines4/5

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

It gives clear operational context: call it to enumerate chats, and when the page is full pass 'next_cursor' back as 'cursor'. It does not explicitly say when to prefer a sibling (e.g. search_contacts vs this) or when not to use it, so it stops short of full alternative routing.

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