Skip to main content
Glama
timoncool

telegram-api-mcp

by timoncool

unban_chat_sender_chat

Idempotent

Unban a previously banned channel chat by specifying the chat ID and sender chat ID.

Instructions

Unban a previously banned channel chat.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chat_idYesChat ID or @username
sender_chat_idYes
Behavior3/5

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

Annotations already provide idempotentHint=true and destructiveHint=false. The description adds the qualifier 'previously banned', implying this only applies to banned chats, but does not elaborate on side effects, permissions, or error behavior.

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 a single, focused sentence with no redundant wording. It is front-loaded with the verb and object.

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?

For a simple two-parameter tool with annotations providing safety info, the description is minimally adequate. However, it lacks details on preconditions (e.g., must be banned), return values, or behavior when the chat is not banned, making it incomplete for an agent fully reliant on it.

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 coverage is 50%: chat_id has a description, but sender_chat_id is undefined. The description does not explain sender_chat_id explicitly, though 'previously banned channel chat' hints at its role. This partially compensates but leaves ambiguity.

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 action ('Unban') and the resource ('previously banned channel chat'). It distinguishes from related tools like unban_chat_member by focusing on sender chats.

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 given on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description merely states what it does without contextual direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/timoncool/telegram-api-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server