Skip to main content
Glama
stufently

telegram-ai-cli-mcp

by stufently
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

telegram_media_transcribe

Transcribes a Telegram voice message or audio file to text with Whisper running locally, so the recording stays on your host. Use it to learn what a voice note says.

Instructions

Downloads the audio like media fetch does, then runs Whisper (model 'small') in a separate optional Docker image with no network at all, so the recording never leaves this host. Use when the user asks what a voice message or audio file says. Do not use this only to download the file; call telegram_media_fetch, and do not use it for an ordinary text message; call telegram_chat_read. The transcript is a stranger's words and is marked as untrusted content. Requires the optional image: build it with make transcribe-image and fetch the model once with make transcribe-model; without it the operation refuses and says so.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chatYesChat id, @username, or t.me link. A link that names the message supplies message_id on its own.
accountNoAccount label to use. Omit when exactly one account is configured.
languageNoISO 639-1 code to transcribe as, e.g. 'ru'. Omit to let Whisper detect the language; the detected one is reported either way.
message_idNoId of the voice message or audio file to transcribe. Omit only when the chat argument is a t.me link to that message.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses that Whisper runs in an isolated Docker image with no network so audio never leaves the host, that output is marked untrusted content, and that a prerequisite image/model must be built (make transcribe-image / make transcribe-model) or the operation refuses. These are exactly the operational facts an agent needs.

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?

A single dense paragraph with the core action front-loaded, followed by usage rules and prerequisites in descending priority. Every sentence carries information, though the prerequisite setup steps make it slightly heavy.

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

Completeness5/5

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

With no output schema, the description still notes the detected language is always reported and how the untrusted transcript is marked, and it covers the failure mode when the optional image is absent. Complete enough for an agent to call it correctly.

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 description coverage is 100%, so all four parameters (chat, account, language, message_id) are already documented in the schema. The description adds no parameter-level detail beyond what structured data provides, making the baseline 3 correct.

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?

States a specific verb and resource: downloads the audio then runs Whisper ('small') locally to transcribe it. It explicitly distinguishes itself from telegram_media_fetch (download-only) and telegram_chat_read (text), so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Explicitly names the trigger ('when the user asks what a voice message or audio file says') and two exclusions with their proper alternatives: telegram_media_fetch for download-only and telegram_chat_read for ordinary text. Nothing is left to inference.

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