Skip to main content
Glama

Unlink Telegram from the owner's notifications

dosai_disconnect_owner_telegram
Destructive

Stop sending the project's notifications to Telegram (linked by one tap or by the owner's own bot); the bot leaves the staff group by itself. Email and WhatsApp notifications stay. Two steps. 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_disconnect_owner_telegram"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.
confirm_tokenNoLeave empty on the first call: it changes nothing and returns what will happen and a code. Ask the owner; only after their explicit "yes" call again with the same arguments and this code.

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

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

Beyond destructiveHint=true and openWorldHint=false, the description discloses real consequences: the bot leaves the staff group on its own, email and WhatsApp notifications survive, and the call requires an explicit owner 'yes' before the second invocation. That is exactly the kind of side-effect and authorization detail annotations cannot carry.

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?

Three short sentences, front-loaded with the primary effect before the caveats about preserved channels and roles. The parenthetical about linkage methods is useful rather than padding; nothing is redundant.

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?

For a destructive mutation with no output schema, it covers the side effects, preserved state, role requirement, and confirmation protocol, leaving little an agent needs before calling it. The only missing piece is disambiguation from dosai_disconnect_telegram, which is minor against otherwise complete coverage.

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 the confirm_token description already explains the empty-first-call dry run and the follow-up with the returned code. The description's 'Two steps' reinforces that behavior but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

It states a specific verb and resource with scope: stop sending the project's Telegram notifications, and it clarifies which channels are unaffected (email and WhatsApp stay). One gap: the sibling dosai_disconnect_telegram is never mentioned, so the agent has no wording to decide between the two disconnect variants.

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?

It gives clear preconditions ('Requires admin or owner role') and flags that the operation is a two-step confirmation flow, which the confirm_token parameter then details. It stops short of naming an alternative tool or saying explicitly when not to call it (for example when Telegram was never connected).

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