Skip to main content
Glama
Telegram Live MCP

Telegram Live MCP

by sugestr

get_forum_topic

Read-only

Retrieves the current title of a Telegram forum topic from a chat ID and exact message_thread_id, so you can confirm the correct topic referenced by message metadata.

Instructions

Проверить точный forum-topic одного чата по message_thread_id и вернуть его актуальное название. ID берётся из read_chat/search_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>",
      "message_thread_id": "<message_thread_id>"
    },
    "name": "get_forum_topic"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idYesиз find_dialogs
message_thread_idYesточный id темы из metadata сообщения

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds value beyond them by stating the return is the topic's current name and that the thread ID must be exact rather than inferred, which tells the agent how to avoid a failed call.

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?

Two short sentences, front-loaded with the action and result, followed by the sourcing constraint and the prohibition. No filler; the only mild redundancy is restating that the topic belongs to a single chat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read-only lookup with full schema coverage and complete annotations, this covers purpose, input sourcing, prohibited usage and the returned value. Only minor gaps remain, such as behavior when the thread does not exist or is not a forum topic.

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 100% and both parameters are documented in the schema (chat_id from find_dialogs, message_thread_id from message metadata). The description reinforces that message_thread_id must be exact and not guessed, but adds no format or edge-case detail beyond that.

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?

States a specific verb and resource: verify the exact forum topic of one chat by message_thread_id and return its current name. The scope (one chat, one exact thread) is clear enough to distinguish it from broad lookups like read_chat or search_chat, though it does not name those as alternatives for the lookup itself.

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?

Explicitly says where the ID comes from (read_chat/search_chat) and forbids two failure modes: guessing the thread or falling back to the group root. That is real when-to-use and when-not-to-use guidance, short of naming a full alternative tool for other cases.

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