Skip to main content
Glama
Sign In
telegram-mcp

telegram-mcp

by draiqw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

tg_topic_edit

Control Telegram forum topics by renaming, closing, hiding, or pinning them to organize your chats.

Instructions

Rename a forum topic, close/reopen it, hide it, or pin it.

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>",
      "topic_id": "<topic_id>"
    },
    "name": "tg_topic_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
titleNo
closedNo
hiddenNo
pinnedNo
topic_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so description must carry behavioral disclosure. It lists the operations but doesn't explain that null values leave fields unchanged, that it's a mutating operation, or any side effects/reversibility. This is a significant gap for a mutation tool.

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?

A single, front-loaded sentence lists all operations without redundancy. It is appropriately sized and easy to parse.

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?

For a 6-parameter mutation tool, the description lacks crucial guides: null semantics, need for chat/topic_id, and potential conflicts when combining fields. Output schema covers return values, but effective invocation depends on understanding optionality.

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?

The description maps each verb to a parameter (rename→title, close→closed, hide→hidden, pin→pinned), adding semantics beyond the schema. However, it doesn't explain the role of chat and topic_id, nor the nullable 'leave unchanged' behavior, so coverage remains incomplete.

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?

Description uses specific verbs ('Rename', 'close/reopen', 'hide', 'pin') with resource 'forum topic', clearly identifying the tool's function. It distinguishes from siblings like tg_topic_create (creation) and tg_pin (message pinning).

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 when/when-not guidance or alternatives are mentioned. The intended use is implied by the action list, but there's no clarification about when to choose this over tg_edit or tg_pin for topic-related operations.

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