Skip to main content
Glama

Link Telegram for the owner's notifications (one tap)

dosai_connect_owner_telegram
Destructive

The simple way to get notifications in Telegram, no @BotFather needed. Returns two one-time links (valid 30 minutes): private_url for the owner's own Telegram (he opens it and presses Start), group_url to pick a staff group. Give the owner the one he wants as a clickable link; a new call cancels the previous links. Whoever opens the link receives the project's notifications, so it goes to the owner only. Then check with dosai_get_owner_telegram and send a test with dosai_send_test_notification. Requires admin or owner role.

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

Input Schema

NameRequiredDescriptionDefault
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.4/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and openWorldHint=true, and the description earns real credit by explaining why: links are one-time with a 30-minute expiry, and a new call cancels the previous links, which is the destructive side effect made explicit. It also discloses the security-relevant behavior that whoever opens the link receives the project's notifications, plus the role requirement — context the annotations cannot convey.

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?

Front-loaded with the value proposition and the returned links before the operational rules, and nearly every sentence carries actionable content. There is minor redundancy ('so it goes to the owner only' restates the prior clause) and the sentence order jumps between returns, delivery advice, and verification steps.

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 compensates by naming both returned links and their expiry, and it covers prerequisites, follow-up verification tools, and the cancellation side effect. For a single-parameter setup tool this is sufficient for an agent to call it and act on the result 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% and there is only one parameter (project_id), already documented as coming from dosai_list_projects. The description adds no further meaning about the parameter, but the schema carries the full burden, so the baseline applies.

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 (link Telegram for the owner's notifications) and immediately distinguishes itself from the alternative route with 'no @BotFather needed'. It goes further by naming the two outputs (private_url, group_url), so an agent knows both what the tool does and what it produces before opening the schema.

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?

Gives clear sequencing guidance: call this, then verify with dosai_get_owner_telegram and send a test with dosai_send_test_notification, and notes the admin/owner role prerequisite. The only gap is that it never explicitly contrasts with the sibling dosai_connect_owner_telegram_bot (the @BotFather variant), leaving that routing choice to inference.

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