Skip to main content
Glama
wazap-mcp

wazap-mcp

by razvangirgiz

Link a WhatsApp account

link_account

Pairs wazap with a user's WhatsApp account when status shows not linked, logged out, corrupt session, or auth failure by returning a pairing code and status polling instructions.

Instructions

Pair wazap with the user's WhatsApp when get_status says not_linked, logged_out, session_corrupt or auth_failure. Show the user the code it returns: WhatsApp → Settings → Linked devices → Link a device → Link with phone number instead. Then poll get_status every 10 s until connected.

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": {
      "phone": "<phone>"
    },
    "name": "link_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYese.g. +15550100
account_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.7.4
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  2. Changed1 schema field changedv1.6.0
    • removedInput schema / properties / account_id / description
      Removed value: -"Account id"
  3. Changed2 schema fields changedv1.0.3
    • changedInput schema / properties / account_id / description
      Previous value: -"Registry account id (default, work, …). Omit to resolve from chat_id or message_id, or the default account."New value: +"Account id"
    • changedInput schema / properties / phone / description
      Previous value: -"International format, e.g. +15550100"New value: +"e.g. +15550100"
  4. Addedv0.15.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare this is a non-read-only, non-idempotent, open-world operation; the description goes well beyond them by disclosing that the call returns a pairing code, that the code must be surfaced to the user with a specific WhatsApp menu path, and that connection is confirmed asynchronously by polling. That is exactly the extra context an agent needs for a stateful pairing flow.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the trigger condition, then the user-facing step, then the follow-up loop. Every sentence carries actionable information with no filler.

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?

For a two-parameter tool with no output schema, the description covers the return value (a code), the human-in-the-loop procedure, and the completion check. The only real omission is the meaning and purpose of account_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%, and the description never mentions either parameter. phone gets a format example in the schema, but account_id is entirely undocumented in both places, so the description does nothing to close the gap.

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?

The description uses a specific verb (pair) and resource (wazap with the user's WhatsApp), and explicitly distinguishes this from get_status by naming that sibling as the trigger source. An agent can tell what this tool does and what it does not do without 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It enumerates exact preconditions: get_status must report not_linked, logged_out, session_corrupt, or auth_failure. It also gives the required post-call loop (poll get_status every 10 s until connected), so both when-to-use and what-to-do-next are explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.