Skip to main content
Glama
Sign In
kotlogramme

kotlogramme

by J0s3f
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

List chat members

telegram_list_members
Read-onlyIdempotent

Lists members of a Telegram group or channel with IDs, names, usernames and roles, returning a cursor for pagination when more results are available.

Instructions

Lists the members of a group or channel with id, name, @username and role. When the page is full the result has 'next_cursor'; pass it back as 'cursor' for more.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chat": "<chat>"
    },
    "name": "telegram_list_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYesThe chat: 'me' for Saved Messages, an @username, or a numeric chat id as listed by telegram_list_chats. Invite links are not accepted.
limitNoHow many members 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

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, openWorld behavior, so the safety profile is covered. The description adds value beyond that by disclosing the pagination mechanic and the shape of each returned member record, which is important since there is no output schema. It does not mention permission requirements or what happens in large channels, but it covers the core behavior an agent needs.

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?

Two tight sentences, both front-loaded: what is returned first, then the pagination contract. Nothing is redundant with the title, and no sentence could be dropped without losing information.

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 simple three-parameter read tool with rich annotations and no output schema, the description supplies the return fields and the pagination loop, which is the main thing an agent could get wrong. Minor omissions remain, such as whether bots are included, what role values look like, and whether membership visibility requires admin rights.

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%, so the baseline would be 3; the description earns a bump because it explains the cursor round-trip explicitly ('the result has next_cursor; pass it back as cursor'), which links a return value to an input parameter in a way the schema alone does not. It says nothing extra about 'chat' or 'limit', but those are already fully documented in the schema.

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 opens with a specific verb and resource ('Lists the members of a group or channel') and enumerates the returned fields (id, name, @username, role), so an agent knows exactly what the tool produces. It stops short of differentiating itself from close siblings such as telegram_list_contacts or telegram_get_member_rights, but the 'members of a chat' framing is distinctive enough to avoid confusion.

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

Usage Guidelines3/5

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

The description gives one concrete usage instruction: when the page is full, take 'next_cursor' and pass it back as 'cursor'. That is a real procedural hint. However, it offers no guidance on when to choose this over telegram_list_contacts, telegram_list_chats, or telegram_get_member_rights, so selection between siblings is left to inference.

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