Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by draiqw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tg_topic_create

Create a forum topic in a Telegram supergroup that supports topics. Provide chat and title, optionally choose an icon emoji.

Instructions

Create a forum topic in a supergroup that has topics enabled.

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>",
      "title": "<title>"
    },
    "name": "tg_topic_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
titleYes
icon_emoji_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations available, the description carries the burden of behavioral disclosure. It does disclose the key precondition that topics must be enabled in the supergroup, which is valuable. However, it does not mention permission requirements, side effects, or behavior if the precondition is not met.

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 concise sentence that is front-loaded with the action and resource. Every word serves a purpose, making it highly efficient.

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?

The description covers the essential purpose and a key constraint, but lacks parameter explanations and usage alternatives. For a tool with three parameters and no annotations, an agent would need more details about chat identifiers and icon emoji format to invoke it correctly. The presence of an output schema reduces the need to describe return values.

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?

Schema description coverage is 0%, so the description must compensate, but it does not explain the meaning or expected format of 'chat', 'title', or 'icon_emoji_id'. 'Title' is somewhat implied by 'forum topic', but 'chat' and 'icon_emoji_id' are left entirely to their minimal schema names.

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 uses the specific verb 'Create' and identifies the resource 'forum topic' with the scope 'in a supergroup that has topics enabled'. This clearly distinguishes it from siblings like tg_topic_edit and tg_topics.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool: only in a supergroup that has topics enabled. This implies the prerequisite but does not explicitly mention alternatives or when not to use it, though the verb 'create' differentiates it from edit tools.

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