Skip to main content
Glama
Sign In
telegram-mcp-connector

telegram-mcp-connector

by nitatsuu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Chat Info

get_chat_info
Read-only

Retrieve Telegram chat or person details, including bio, description, and member count, by chat ID, @username, t.me link, or title.

Instructions

Details about a chat or person: bio/description, member count, etc.

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

Input Schema

NameRequiredDescriptionDefault
chatYesChat id, @username, t.me link, "me", or chat title

Output Schema

NameRequiredDescriptionDefault

No arguments

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 and openWorldHint=true, so the safety profile is covered and the bar is lower. The description adds a small amount of behavioral context by indicating the response covers profile-style fields (bio, member count), but says nothing about privacy restrictions, what happens when the identifier resolves to a person versus a chat, or failure modes for unresolvable titles.

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 tight sentence with no padding, front-loaded with what is returned. The vague catch-all 'etc.' is the only element that doesn't earn its place, since it signals incompleteness rather than information.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. However, for a lookup tool with open-world resolution and multiple accepted identifier forms, the description does not address what happens when a name is ambiguous or unresolvable, nor how person results differ from chat results—leaving meaningful gaps.

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 description coverage is 100%, so the single 'chat' parameter's accepted formats (id, @username, t.me link, "me", title) are fully documented in the schema. The description's phrase 'chat or person' is a marginal addition, clarifying that user identifiers are also valid, but it doesn't explain resolution ambiguity (e.g., title collisions).

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

Purpose3/5

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

The description names the resource (a chat or person) and hints at returned fields (bio/description, member count), but 'Details about' is not a specific verb and the trailing 'etc.' leaves the scope open. An agent can guess this is a metadata lookup rather than a message fetch, but the differentiation from siblings like list_chats or whoami is left implicit.

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?

No when-to-use guidance is given: nothing says to call this for profile/metadata lookups versus list_chats for enumerating chats or whoami for the current account. The only usage signal is indirect, via the 'me' value documented in the schema. No exclusions or alternatives are mentioned.

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