Skip to main content
Glama
Sign In
Telegram MCP

Telegram MCP

by Anonymouse8882
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_chat_info

Retrieve detailed information about a Telegram chat, including its description, member count, pinned message ID, and permissions.

Instructions

获取某个对话的详细信息（简介、成员数、置顶消息 ID、权限等）。

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
chatYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations exist; description carries the burden. It lists example outputs but does not explicitly state read-only behavior, auth requirements, or rate limits. Adequate but not detailed.

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 concise sentence, front-loaded with purpose. No redundant text. Could benefit from a more structured format, but efficient overall.

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?

Output schema exists, so return details are covered. However, missing parameter guidance and usage context make it borderline adequate for a tool of low complexity.

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

Parameters1/5

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

Schema coverage is 0%, and the description provides no explanation of the 'chat' parameter, such as accepted formats (ID vs username) or constraints. Fails to add value beyond the schema.

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 clearly states the tool's purpose: get detailed chat info (intro, member count, pinned message ID, permissions). It distinguishes from sibling tools like get_participants or set_chat_title.

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?

No explicit guidance on when to use vs alternatives. Usage is implied for retrieving chat details, but no exclusions or context criteria are provided.

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