Fast MCP Telegram

Get chat info

get_chat_info

Read-onlyIdempotent

Retrieve profile and metadata for any Telegram chat: user, bot, group, or channel. For forum chats, also list up to 20 topics.

Instructions

Load profile and metadata for one user, bot, group, or channel. Success: info dict; forum chats may include topics up to topics_limit. Full documentation: https://github.com/leshchenko1979/fast-mcp-telegram/blob/main/docs/Tools-Reference.md

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chat_id`	Yes	Target chat: numeric id (e.g. -100…), username without @, or 'me' for Saved Messages.
`topics_limit`	No	Max forum topics to list when the chat is a forum.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`error`	No
`operation`	No
`code`	No
`params`	No
`exception`	No
`action`	No
`error_code`	No
`id`	No
`title`	No
`username`	No
`first_name`	No
`last_name`	No
`phone`	No
`is_forum`	No
`is_channel`	No
`is_group`	No
`is_user`	No
`is_bot`	No
`participants_count`	No
`topics`	No
`topics_has_more`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.36.0Jun 18, 2026

removedOutput schema / additionalProperties
```
Removed value: -true
```

addedOutput schema / description

Added value: +"Return type for ``get_chat_info``."

addedOutput schema / properties

Added value: +{
+  "action": {
+    "type": "string"
+  },
+  "code": {
+    "type": "integer"
+  },
+  "error": {
+    "type": "string"
+  },
+  "error_code": {
+    "type": "string"
+  },
+  "exception": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "first_name": {
+    "type": "string"
+  },
+  "id": {
+    "type": "integer"
+  },
+  "is_bot": {
+    "type": "boolean"
+  },
+  "is_channel": {
+    "type": "boolean"
+  },
+  "is_forum": {
+    "type": "boolean"
+  },
+  "is_group": {
+    "type": "boolean"
+  },
+  "is_user": {
+    "type": "boolean"
+  },
+  "last_name": {
+    "type": "string"
+  },
+  "ok": {
+    "type": "boolean"
+  },
+  "operation": {
+    "type": "string"
+  },
+  "params": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "participants_count": {
+    "type": "integer"
+  },
+  "phone": {
+    "type": "string"
+  },
+  "title": {
+    "type": "string"
+  },
+  "topics": {
+    "items": {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "topics_has_more": {
+    "type": "boolean"
+  },
+  "username": {
+    "type": "string"
+  }
+}

First observedv0.21.0May 28, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare read-only, idempotent, and open-world behavior. The description adds that the result is an info dict and that forum chats may include topics up to the specified limit, providing some additional behavioral context. However, it does not disclose error handling, permissions, or rate limits.

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?

The description is three sentences: the first states the core purpose, the second summarizes success output and special forum behavior, and the third provides a documentation link. It is front-loaded, efficient, and free of redundant content.

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 simple two-parameter tool with high schema coverage, full annotations, and an existing output schema, the description is sufficiently complete. It covers the purpose, return type, and special forum behavior without needing to explain return values in detail. The documentation link also supplements any missing specifics.

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 description adds meaning by specifying that the target can be a user, bot, group, or channel, which clarifies the chat_id parameter domain. It also reinforces the topics_limit behavior for forums, going slightly beyond the schema descriptions.

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 uses a specific verb ('Load') and identifies the resource ('profile and metadata for one user, bot, group, or channel'), making the tool's function explicit. It clearly distinguishes from siblings like get_messages and find_chats by specifying it targets a single chat entity.

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 implies when to use the tool (when you need profile/metadata for a specific chat) but does not explicitly mention alternatives or when not to use it. No exclusions or references to sibling tools are provided, so guidance is only implied.

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

Install Server