Skip to main content
Glama

Disconnect WhatsApp

dosai_disconnect_whatsapp
Destructive

Unlink the WhatsApp number from the bot, QR or official: the bot stops answering there at once. A QR number comes back with a new QR or code, an official one only through the Meta window (dosai_get_whatsapp_connect_link). Two steps. Admin or owner.

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_whatsapp"
  }
}

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

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description goes well beyond them: it discloses the immediate effect ("the bot stops answering there at once") and the divergent recovery cost for QR versus official numbers. That asymmetry is exactly the information an agent needs before running a destructive action.

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 effect and recovery consequences before the procedural and permission notes; no filler sentences. The phrasing "Unlink the WhatsApp number from the bot, QR or official" is slightly compressed/ambiguous on first read, and the fragmentary "Two steps. Admin or owner." relies on the schema to be fully parsed.

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, two-parameter tool with no output schema, the description covers impact, per-variant recovery path, escalation route to the reconnect sibling, authorization level, and the confirmation protocol. Nothing an agent needs before invoking it is missing.

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 spells out the empty-first-call then confirm-with-code protocol in detail. The description's "Two steps" reinforces that flow but adds no new syntax or semantics beyond what the schema provides, so the baseline 3 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 ("Unlink the WhatsApp number from the bot") and immediately splits the resource into its two variants (QR vs official), which is the distinction that matters for this operation. An agent can tell it apart from sibling disconnect tools for Instagram/Telegram/CRM by name alone.

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 routes the reconnect path: a QR number comes back with a new QR/code, while an official number can only be re-linked via dosai_get_whatsapp_connect_link — naming the sibling and the condition that selects it. It also states the prerequisite ("Admin or owner") and the two-step confirmation requirement, so the agent knows who must authorize and that a second call is expected.

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