Skip to main content
Glama

Link to connect WhatsApp

dosai_get_whatsapp_connect_link
Destructive

A page where the owner connects WhatsApp: by QR (open on a computer or another phone, scan from the business phone) or officially through Meta (Facebook login; a WhatsApp Business number or a SIM with no WhatsApp; the only path to the official channel). Whoever opens the link can attach THEIR number to the bot, so give it only to the owner; a new link kills the old one. Lives 14 days. 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_get_whatsapp_connect_link"
  }
}

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?

Goes well beyond the annotations: it explains why destructiveHint is true ("a new link kills the old one"), the 14-day lifetime, that whoever opens the link can attach THEIR number, that access is restricted to admin/owner, and that the operation is two-stepped. This is exactly the context an agent needs before calling a mutating link-generation tool.

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-loads what the tool does and packs the security, lifetime, and flow warnings into a few dense fragments. The telegraphic style is efficient, though the run of parenthetical asides makes it slightly harder to scan than a cleanly structured alternative.

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 two-parameter tool with no output schema, the definition covers purpose, both connection paths, confirmation flow, link lifetime, invalidation behavior, and authorization – nothing essential to correct invocation 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%, so both parameters are already documented, including the confirm_token confirmation protocol. The description reinforces this with "Two steps" but adds little new meaning beyond what the schema states, so 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?

States a concrete verb and resource – a page/link the owner uses to connect WhatsApp – and even enumerates the two connection paths (QR scan vs. official Meta/Facebook login). It is not explicitly contrasted with the closely related dosai_get_whatsapp_pairing_code sibling, so an agent must still infer which link to fetch.

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 real when-to-use context: two-step flow, first call with empty confirm_token to preview, second call only after the owner's explicit "yes", and the audience constraint (admin or owner, and give the link only to the owner). It does not name an alternative tool for cases where this link is the wrong choice.

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