Skip to main content
Glama

The owner's OWN Telegram bot for notifications or reports

dosai_get_owner_telegram_bot
Read-onlyIdempotent

Only for an owner who uses his OWN bot from @BotFather (most link Telegram by one tap: dosai_get_owner_telegram). Is that bot connected (purpose notifications or reports), its @username, the chat it writes to, and for notifications whether the last one was delivered and why not. 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_get_owner_telegram_bot"
  }
}

Input Schema

NameRequiredDescriptionDefault
purposeYes
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.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety burden is low. The description adds access-control context ('Owner only') and discloses the returned diagnostic content (whether the last notification was delivered and why not), which is real value beyond the annotations. It stops short of describing failure modes when no bot is connected.

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?

Very compact: the owner-only restriction and the sibling alternative are front-loaded where they matter most, and every clause carries content. The telegraphic sentence fragments ('Is that bot connected ... its @username, the chat it writes to') read awkwardly but cost little space.

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?

With no output schema, the description must carry return information, and it does by listing connected state, @username, destination chat, and delivery diagnostics. Combined with annotations covering safety and a small two-parameter schema, an agent has enough to call it correctly; only not-connected/error behavior is left unstated.

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 50%: project_id is documented in the schema, but the purpose enum carries no explanation for its values. The description compensates by showing the enum's effect, noting that purposes are 'notifications or reports' and that delivery diagnostics apply to the notifications purpose specifically — meaning added beyond the raw enum list.

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?

The description names a specific resource (the owner's own @BotFather bot) and enumerates what is returned: connected state, @username, target chat, and last-notification delivery status. It explicitly separates itself from dosai_get_owner_telegram ('most link Telegram by one tap'). The slightly fragmented, question-like phrasing ('Is that bot connected...') makes the read action less immediately parseable than a clean verb+resource statement, so it falls short of a 5.

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?

It gives an explicit precondition ('Only for an owner who uses his OWN bot from @BotFather') and names the alternative for the common case ('most link Telegram by one tap: dosai_get_owner_telegram'), which is exactly the when-to-use vs when-to-use-something-else routing an agent needs.

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