aiogram-mcp

by Py2755

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

get_chat_info

Retrieve detailed information about a Telegram chat by providing its unique chat ID.

Instructions

Get details about a chat.

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_id": "<chat_id>"
    },
    "name": "get_chat_info"
  }
}

Input Schema

Name	Required	Description	Default
`chat_id`	Yes

Output Schema

Name	Required	Description	Default
`ok`	Yes
`error`	No
`id`	No
`type`	No
`title`	No
`username`	No
`description`	No
`member_count`	No
`is_forum`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedMay 3, 2026

addedOutput schema / properties / title

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedv0.7.1Mar 16, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavior. It only states 'Get details' without mentioning that it is read-only, potential error conditions, or required permissions. This is minimal disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise. However, it is too brief and lacks informative content that could fit without losing conciseness.

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?

Given that an output schema exists, the description does not need to explain return values. However, for a tool with one required parameter and many siblings, it is minimally complete but could include hints about the nature of the details.

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 input schema has a single parameter 'chat_id' with no description, and the tool description adds no meaning beyond that. The parameter is simply an integer, but no context (e.g., what it represents) is provided.

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 clearly states 'Get details about a chat,' which indicates the verb and resource. It is distinct from sibling tools like get_chat_member_info or get_chat_members_count, but could be more specific about what details are included.

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 guidance is provided on when to use this tool versus alternatives, such as when to use get_chat_info over get_chat_member_info or get_bot_info. The context is implied by the tool name only.

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