Skip to main content
Glama

Connect the owner's OWN Telegram bot for notifications or reports

dosai_connect_owner_telegram_bot
Destructive

The long way, only when the owner wants messages from his OWN bot: otherwise use dosai_connect_owner_telegram (one tap, no @BotFather; reports go there too). Connects a bot that writes to the OWNER: purpose=notifications (new dialogs, payments, errors) or purpose=reports (scheduled reports). It is a separate bot from the one clients write to. Steps for the owner: create a bot in @BotFather (/newbot) and paste its key here; open the new bot and press Start, or add it to the work group; give the chat: the group's numeric id or a public @username. Pass send_test=true to save and immediately send a test message there. The key passes through this chat, warn the owner. Owner only.

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": {
      "project_id": "<project_id>",
      "purpose": "<purpose>"
    },
    "name": "dosai_connect_owner_telegram_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
chat_idNoNumeric chat id or @username.
purposeYes
bot_tokenNoThe key from @BotFather; omit to change only the chat.
send_testNo
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructive and open-world behavior; the description adds real context beyond them: the token is a credential that 'passes through this chat, warn the owner', send_test immediately sends an outbound message, and bot_token may be omitted to change only the chat. It does not say what happens to a previously connected bot (overwrite/replace) or what the response returns, which is the main remaining gap for a destructive operation.

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?

Dense and mostly front-loaded: the routing decision comes first, then the resource, then the setup steps. Minor deductions for the fragmented opener ('The long way, ...') and for burying the access constraint 'Owner only' at the very end rather than alongside the routing guidance.

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?

There is no output schema, so the description carries the burden of explaining outcomes, which it partially does via send_test and the required BotFather/Start steps. It is adequate for a 5-parameter destructive tool, but leaves open how an existing connection is affected and what a successful call yields.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%, and the description compensates well for the weaker fields: purpose values are given concrete meaning with example events, chat_id is disambiguated as a group numeric id or public @username, and bot_token is described with its BotFather source and omit-to-keep semantics. Only project_id is left solely to the schema, which already documents it.

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 ('Connects a bot that writes to the OWNER') and immediately distinguishes it from two siblings: dosai_connect_owner_telegram (one-tap path) and the client-facing bot ('a separate bot from the one clients write to'). The purpose enum is spelled out with concrete event types (new dialogs, payments, errors vs scheduled reports).

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 frames this as the fallback path ('The long way, only when the owner wants messages from his OWN bot') and names the preferred alternative with the reason (one tap, no @BotFather). It also states the audience constraint ('Owner only') and when to pass send_test, so selection and invocation conditions are both covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources