telegram-mcp

Overview Schema Source Related Servers Discussions Admin

chat_info

Retrieve details about any Telegram user, bot, group, or channel by providing its identifier. Use this tool to look up information about a chat entity.

Instructions

Get details about a user, bot, group or channel.

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

Input Schema

Name	Required	Description	Default
`chat`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 22, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are present, so the description carries the full behavioral burden. It only says 'Get details' and lists entity types, but does not disclose what 'details' includes, how the chat value is resolved, or how authorization failures or invalid references behave.

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?

One clean, front-loaded sentence with no filler. It is compact and readable, though so terse that important semantic detail about the chat parameter was omitted.

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

Completeness2/5

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

Despite the simple schema and existing output schema, the definition lacks essential invocation context: what format chat accepts, when to choose this tool over sibling information tools, and what 'details' covers. An agent can guess the broad intent but cannot confidently invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single required parameter, chat, has 0% schema description coverage. The description implies chat can identify a user, bot, group, or channel, but it never states whether the value is an ID, username, or phone number, leaving invocation ambiguous.

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 states the operation precisely: 'Get details' and enumerates the target resource types: 'user, bot, group or channel.' This is clearly distinct from broad tools like list_chats or get_me, though it does not explicitly name any sibling alternatives.

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?

There is no guidance on when to use this tool versus list_chats, get_participants, or get_me. The description only announces what the tool does, not when it should be preferred or what prerequisite information the caller needs.

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